7.4 TSM Management Class Binding and Rebinding Overview


Management Class Binding

Management class Binding is the process of associating a file name with a management class name. Binding associates a file with a management class. When you back up a file for the first time, Tivoli Storage Manager binds it to either the default management class or the management class specified in your include-exclude list. In later full incremental backups of the same file, if you change the management class, both active and inactive versions are bound again to the new management class. However, with selective backup and incremental-by-date backups, the new backups are bound to the new management class, but previous backup versions remain bound to the original management class.

Files are bound to a management class name in the following circumstances
  • A user can bind a file to a specific management class name by using the INCLUDE option on an include-exclude list.
  • A user can bind a file to a management class name by using the ARCHMC option when archiving a file.
  • A user can bind a directory to a management class name by using the DIRMC option when backing up a file. If not specified, by default, the management class in the active policy set of the policy domain that has the longest retention period is used for directories.
  • The client node can bind a file to the default management class in the active policy set when a user does not bind the file to a specific management class name.

Management Class Rebinding

Management class rebinding is the process of associating a file with a new management class name. Backup versions are rebound to a different management class name in the following cases

Also Read: What is TSM Policy Management ?
  • Users change the management class assigned to a file by specifying a different management class in an include-exclude list and performing an incremental or selective backup.
  • An administrator activates a policy that does not contain the management class.
  • An administrator assigns a client node to a different policy domain and the active policy set in the policy domain that does not have a management class with the same name.
Backup versions of a directory can be rebound when the user specifies a different management class using the DIRMC option in the client option file, and when the directory gets backed up.

If a file is bound to a management class that no longer exists, the server uses the default management class to manage the backup versions. When the user does another backup, the server rebinds the file and any backup versions to the default management class. If the default management class does not have a backup copy group, the server uses the backup retention grace period specified for the policy domain.

All backup versions are re-bound to the new MGMTCLASS. If the management class that files are bound to is deleted, Tivoli Storage Manager uses the attributes of the default management class to manage the backup versions.



Archive copies are never rebound because each archive operation creates a different archive copy. Archive copies remain bound to the management class name specified when the user archived them.

If the management class to which an archive copy is bound no longer exists or no longer contains an archive copy group, the server uses the default management class. If you later change or replace the default management class, the server uses the updated default management class to manage the archive copy.

If the default management class does not contain an archive copy group, the server uses the archive retention grace period specified for the policy domain.





What Others are Reading Now...

0 Comment to "7.4 TSM Management Class Binding and Rebinding Overview"

Post a Comment