Troubleshooting
Problem
Changing the retention for some data within a management class without changing the retention for everything.
Cause
It may be necessary at some point to change the retention setting for some of the data in a particular management class but not necessarily all the data. If some of this data has been deleted from the client so only inactive copies exist on the Tivoli Storage Manager/Spectrum Protect server or the data is archived objects, rebinding the data to a new management class through the client's include/exclude list will not work.
Resolving The Problem
One method of changing the retention setting for some (but not all) of the data in a given management class and ensure that the objects which may only have inactive copies in Tivoli Storage Manager/Spectrum Protect server storage are included is to change the domain of the node/client that owns the specific data. Because the backup or archive data is already bound to a specific management class and it is not desirable to change the copy group retention settings for all the data, moving the node/client to a new domain with a management class of the same name with the necessary retention setting will provided the desired results. Alternatively, using the default management class in the new domain would also work. However this will produce messages each time expiration runs indicating that the specific management class does not exist in the new domain so the default will be used.
For example:
MYNODE is defined to the STANDARD domain with the installation default retention values. There are 100 other nodes also defined to this domain. The data for all 101 of these nodes is bound to the STANDARD management class using the default retention settings.
At some point it is determined that the data backed up for MYNODE needs to be kept forever. This includes copies of all the data that has been recently deleted from the client and exists in Tivoli Storage Manager/Spectrum Protect only as inactive data. Because only data for MYNODE needs to be kept forever changing the retention values for the STANDARD policy structure is not an option.
To retain all the currently backed up data for MYNODE a new domain can be created called FOREVER with a management class of STANDARD and all copy group retention values set to no limit. If MYNODE is then update to set its domain to FOREVER all the data bound to the standard management class will now have the retention values of the STANDARD management class in the FOREVER domain instead of the STANDARD management class in the STANDARD domain.
Product Synonym
TSM SP
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21234247