Different Types of Backup Methodologies in TSM:
1) Progressive Incremental Backup: In this method of Backup for the first time TSM takes the full backup of client machine and from next backup on-wards it only takes the backup of new or modified files from the client machine. this method of backup helps us for low disk space and also we can restore faster the version of the file that client needs. based on our versioning parameters specified for that node.
2) Selective Backup: In this method we can take the backup of selected file from the client machine. selective backup is always a full backup. this method helps to take the backup of any important files of the client.
3) Image Backup: In this method we can take the backup of the entire drive from the client machine. and also we can only restore entire drive while restoring. we can restore any single file from image backup. this helps us while restoring entire drive.
4) Journal Based Backup: In this method we need to install Journal engine in the client machine at the time of installation of B/A client software. once we installed journal engine it will create Journal DB in the client machine and if any new file is created or any file gets modified then journal engine tracks those changes and saves a copy of them in Journal DB. and when backup schedule is triggered then TSM Server will automatically contacts Journal DB and takes the backup of those files in the Journal DB. this helps us in backup process to complete faster. and less load on the client machine. Journal engine can only be configured in Windows and AIX machines. and once the backup is completed the files from the Journal DB will get deleted (or) purged (or) truncated.
Parameters in Backup:
1) VERSION EXIST: (verexist)
This parameter defines how many no. of versions of the backup data of frequently modifies file have to be stored. If we mention versionexist=6 then 6 versions of the file which is being modified will be stored in the TSM storage pool and once the 7 version of the file is backed up automatically the first version the file will be deleted. The expired file will be deleted from the TSM server once the expiration inventory process is executed in TSM Server. The latest version of the file is known as active version and all the previous versions is known as inactive versions.
2) VERSION DELETE: (verdelete)
This parameter defines how no. of versions of the file has to be stored once the actual file is deleted from the client machine.
If we mention versiondelete=4 then once the actual file is deleted from the client machine then 4 recent versions of the file or object will be stored in the TSM Server and the remaining versions will be deleted once the expiration inventory process is executed.
3) Retention exist: ( Retexist)
This parameter defines how many no. of days the inactive versions of a unmodified file have to be stored in the TSM server.
If we mention Retexist=60. Then if file is not been modified for 60 days then all the inactive versions of the file will be deleted and only the active version of the file will be stored.
4) RETENTION ONLY: (RETONLY)
This parameter defines how many no. of days the versions of a file to be saved from the time the actual file is deleted from the client machine.
If we mention retonly=120 then the TSM server will maintain the versions of the file for 120 days which is already been deleted from the client machine. And on 121st day all the versions of the file will be deleted from the TSM Server.
5) SERIALIZATION:
This parameter is used in backup copygroup. This parameter is applicable for open files in the client machine. Open files are those files which are being used or processed by any user or application. While taking backup of the client machine then TSM server treats these open files in 4 different ways. They are:
a) Static:
In this mechanism while backup is running if any of the file is open then the TSM Server will skip the file from Backup and an error will be raised mentioning that the supposed file is not backed up due to that file was open at the time of backup.
b) Shared static:
In this mechanism TSM Server tries to access the file for 4 times to take the backup of the file at regular intervals and the interval time between each attempt will be default taken by TSM server itself depends on the data to be backed up. If during the fourth attempt also the file is still open then the TSM Server skips the file from backup and raises an error mentioning that the file was open during the backup schedule so that it is not backed up.
In real-time we mention the serialization parameter as Shared Static.
c) DYNAMIC:
In this mechanism if a file is in open state during the backup schedule then also the TSM Server will take the backup of the file @ the first time only regardless of the file being used or not.
d) SHARED DYNAMIC:
In this mechanism if a file is in open state during the backup schedule then the TSM Server tries to access the file for 4 times with regular intervals and if the fourth time also file is still open the @ the fourth time TSM Server will take the backup the file regardless of the file is still open or not.
1) Progressive Incremental Backup: In this method of Backup for the first time TSM takes the full backup of client machine and from next backup on-wards it only takes the backup of new or modified files from the client machine. this method of backup helps us for low disk space and also we can restore faster the version of the file that client needs. based on our versioning parameters specified for that node.
2) Selective Backup: In this method we can take the backup of selected file from the client machine. selective backup is always a full backup. this method helps to take the backup of any important files of the client.
3) Image Backup: In this method we can take the backup of the entire drive from the client machine. and also we can only restore entire drive while restoring. we can restore any single file from image backup. this helps us while restoring entire drive.
4) Journal Based Backup: In this method we need to install Journal engine in the client machine at the time of installation of B/A client software. once we installed journal engine it will create Journal DB in the client machine and if any new file is created or any file gets modified then journal engine tracks those changes and saves a copy of them in Journal DB. and when backup schedule is triggered then TSM Server will automatically contacts Journal DB and takes the backup of those files in the Journal DB. this helps us in backup process to complete faster. and less load on the client machine. Journal engine can only be configured in Windows and AIX machines. and once the backup is completed the files from the Journal DB will get deleted (or) purged (or) truncated.
Parameters in Backup:
1) VERSION EXIST: (verexist)
This parameter defines how many no. of versions of the backup data of frequently modifies file have to be stored. If we mention versionexist=6 then 6 versions of the file which is being modified will be stored in the TSM storage pool and once the 7 version of the file is backed up automatically the first version the file will be deleted. The expired file will be deleted from the TSM server once the expiration inventory process is executed in TSM Server. The latest version of the file is known as active version and all the previous versions is known as inactive versions.
2) VERSION DELETE: (verdelete)
This parameter defines how no. of versions of the file has to be stored once the actual file is deleted from the client machine.
If we mention versiondelete=4 then once the actual file is deleted from the client machine then 4 recent versions of the file or object will be stored in the TSM Server and the remaining versions will be deleted once the expiration inventory process is executed.
3) Retention exist: ( Retexist)
This parameter defines how many no. of days the inactive versions of a unmodified file have to be stored in the TSM server.
If we mention Retexist=60. Then if file is not been modified for 60 days then all the inactive versions of the file will be deleted and only the active version of the file will be stored.
4) RETENTION ONLY: (RETONLY)
This parameter defines how many no. of days the versions of a file to be saved from the time the actual file is deleted from the client machine.
If we mention retonly=120 then the TSM server will maintain the versions of the file for 120 days which is already been deleted from the client machine. And on 121st day all the versions of the file will be deleted from the TSM Server.
5) SERIALIZATION:
This parameter is used in backup copygroup. This parameter is applicable for open files in the client machine. Open files are those files which are being used or processed by any user or application. While taking backup of the client machine then TSM server treats these open files in 4 different ways. They are:
a) Static:
In this mechanism while backup is running if any of the file is open then the TSM Server will skip the file from Backup and an error will be raised mentioning that the supposed file is not backed up due to that file was open at the time of backup.
b) Shared static:
In this mechanism TSM Server tries to access the file for 4 times to take the backup of the file at regular intervals and the interval time between each attempt will be default taken by TSM server itself depends on the data to be backed up. If during the fourth attempt also the file is still open then the TSM Server skips the file from backup and raises an error mentioning that the file was open during the backup schedule so that it is not backed up.
In real-time we mention the serialization parameter as Shared Static.
c) DYNAMIC:
In this mechanism if a file is in open state during the backup schedule then also the TSM Server will take the backup of the file @ the first time only regardless of the file being used or not.
d) SHARED DYNAMIC:
In this mechanism if a file is in open state during the backup schedule then the TSM Server tries to access the file for 4 times with regular intervals and if the fourth time also file is still open the @ the fourth time TSM Server will take the backup the file regardless of the file is still open or not.