Rebinding is the process of associating all versions of a file or a logical volume image with a new management class.
The server rebinds backup versions of files and logical volume images in some cases.
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.
The most recently backed up files are active backup versions. Older copies of your backed up files are inactive backup versions. You can configure management classes to save a predetermined number of copies of a file. If a management class is saving five backup copies, there would be one active copy saved and four inactive copies saved. If a file from one management class is bound to a different management class that retains a lesser number of files, inactive files are deleted.
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.
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.