Selective: The selective command backs up files that you specify. If these files become damaged or lost, you can replace them with backup versions from the server. When you run a selective backup, TSM backs up all the files unless they are excluded from backup in your include-exclude list, or they do not meet management class requirements for serialization.
During a selective backup, TSM sends copies of the files to the server even if they have not changed since the last backup. This might result in more than one copy of the same file on the server. If this occurs, you might not have as many different down-level versions of the file on the server as you intended. Your version limit might consist of identical files. To avoid this, use the incremental command to back up only new and changed files. You can selectively back up single files or directories. You can also use wildcard characters to back up groups of related files. During a selective backup, a directory path may be backed up, even if the specific file that was targeted for backup is not found. For example: dsmc selective "/dir1/dir2/bogus.txt" still backs up dir1 and dir2 even if the file bogus.txt does not exist.
If the selective command is retried because of a communication failure or session loss, the transfer statistics will display the number of bytes TSM attempts to transfer during all command attempts. Therefore, the statistics for bytes transferred may not match the file statistics, such as those for file size.
Incremental: The incremental command backs up all new or changed files or directories in the default client domain or from file systems, directories, or files you specify that are not excluded from backup services. To incrementally back up selected files or directories, specify the file specification in the command. The default is to back up files or directories in the default domain.
The following attributes in the management class assigned to the file or directory affect whether the data is actually backed up:
Frequency - The number of days that must elapse between successive backups for the file. This attribute is only used during a full incremental backup.
Mode - Permits you to back up only files that changed since the last backup (modified), or to back up the files whether they changed or not (absolute).
Serialization - Permits or denies backup of files or directories according to the following values:
static: In order to be backed up, data must not be modified during backup or archive.
shrstatic: If data in the file or directory changes during each of the four attempts to back up or archive it, it is not backed up or archived.
dynamic: The object is backed up or archived on the first attempt whether or not data changes during the process.
shrdynami: The object is backed up or archived on the last attempt, even if data changes during the process.
You can assign the default management class to a file, or you can assign a specific management class to a file using the include option in an include-exclude list.
You can perform either a full incremental backup or an incremental by date backup. The default is a full incremental backup. You can also the selective command to perform a selective backup that backs up only the files, directories or empty directories that you specify.
A full incremental backs up all files or directories that are new, or have changed since the last incremental backup. During a full incremental backup, the client queries the server to determine the exact condition of your storage. TSM uses this information to:
Back up new files or directories.
Back up files or directories whose contents have changed.
Mark inactive backup versions on the server for files or directories that are deleted from the workstation.
Rebind backup versions to management classes if the management class assignments change.
An incremental-by-date backup, backs up new and changed files with a modification date later than the date of the last incremental backup stored at the server, unless the files are excluded from backup by an exclude statement. If an incremental-by-date is performed on only part of a file system, the date of the last full incremental is not updated, and the next incremental-by-date will back up these files again. Therefore, changes to the access control lists (ACL) are not backed up during an incremental-by-date. Use the query filespace command to determine the date and time of the last incremental backup of the entire file system.
To perform an incremental-by-date backup, use the -incrbydate option with the incremental command.
Unlike a full incremental, an incremental-by-date does not maintain current server storage of all your workstation files because:
It does not expire backup versions of files that are deleted from the workstation.
It does not rebind backup versions to a new management class if the management class has changed.
It does not back up files with attributes that have changed, unless the modification dates and times have also changed.
It ignores the copy group frequency attribute of management classes.
For these reasons, it is recommended that if you have limited time during the week to perform backups, but extra time on the weekends, you can use a partial incremental backup on weekdays, and a full incremental backup on weekends to maintain current server storage of your workstation files. If the incremental command is retried because of a communication failure or session loss, the transfer statistics will display the number of bytes TSM attempted to transfer during all commands attempts. Therefore, the statistics for bytes transferred may not match the file statistics, such as those for file size.
The following are examples of tasks you might perform using the incremental command.
Task Run an incremental backup of the default client domain specified in your client options file.
Command: Incremental
Task Run an incremental backup for the /home, /usr, and /proj file systems.
Command: Incremental /home /usr /proj
Task Run an incremental backup for the /proj/test directory.
Command: Incremental /proj/test/
Task Run an incremental-by-date backup for the /home file system.
Command: Incremental -incrbydate /home
Task Run an incremental backup of all files in the /fs/dir1 directory that begin with the string abc.
Command: Incremental -subdir=yes "/fs/dir1/abc*"
Task Run an incremental backup of the abc file in the /fs/dir1 directory.
Command: Incremental -subdir=yes /fs/dir1/abc
Task Run an incremental backup of the directory object /fs/dir1, but not any of the files in the /fs/dir1 directory.
Command: Incremental -subdir=yes /fs/dir1
Task Run an incremental backup of the directory object /fs/dir1 and all of the files in the /fs/dir1 directory.
Command: Incremental -subdir=yes /fs/dir1/
Restore commands:
Task Restore a single file named budget.
Command: restore /home/devel/projecta/budget
Task Restore a single file named budget.finbudget which resides in the current directory.
Command: restore file budget
Task Restore all files with a file extension of .c from the /home/devel/projecta directory.
Command: restore "/home/devel/projecta/*.c"
Task Restore files in the /user/project directory. Use the pick and inactive options to select active and inactive backup versions.
Command: restore "/user/project/*" –pick –inactive
Task Restore all files from the /home/devel/projecta directory that end with the character .c to the /home/newdevel/projectn/projecta directory. If the projectn or the projectn/projecta directory does not exist, it is created.
Command: restore "/home/devel/projecta/*.c" /home/newdevel/projectn/
Task Restore all files in the /home/mydir directory to their state as of 1:00 PM on August 17, 1998.
Command: res -pitd=8/17/1998 -pitt=13:00:00 /home/mydir/
Task Restore all objects in the /home/myid/ directory. Since this restore is fully wildcarded, if the restore process is interrupted, a restartable restore session is created. Use the restart restore command to restart a restartable restore session. Use the cancel restore command to cancel a restartable restore session.
Command: res /home/myid/*
No comments:
Post a Comment