Troubleshooting
Problem
HSM for Windows migrated files can expire after 365 days on the Tivoli Storage Manager server. The client should be configured to use a management class with an archive copy group retention value larger than 365 days or a value of NOLIMIT. This Tech Note describes how to figure out the current retention settings and gives some recommendation on how to change them.
Symptom
Tivoli Storage Manager HSM for Windows migrates files to the archive pool on the Tivoli Storage Manager server. The migrated files are bound to the default management class. The default policy values in the archive copy group of the standard management class retain archive copies for only 365 days. If you did not change the retention values, the archive copies can become unavailable after that period of time.
This is also described here: http://www-01.ibm.com/support/docview.wss?rs=2348&uid=swg21330160
The HSM for Windows client will warn you about this situation with the following pop up message at GUI start: "The Tivoli Storage Manager server default management class is time-based and configured to expire your migration file data XXX day(s) after migration"
Determining the current setting for the archive retention period
- Log on to the TSM server
- Determine the current policy domain for your HSM client node by running the command "QUERY NODE"
- Determine the activated default management class for that policy domain with the command "QUERY DOMAIN"
- Determine the Retain Version for the archive copy group of the default management class with the command "QUERY COPYGROUP"
- The value of "Retain Version" is the number of days after migration when the TSM server will expire the objects from the archive.
Resolving The Problem
If you want to keep migrated files longer than 365 days, then extend the retention period of the archive copy group.
You can either achieve this by changing the settings of your default management class of the domain of your HSM client node. This will affect the default for all nodes that are registered to this domain. (See "UPDATE COPYGROUP" command in the Tivoli Storage Manager Administrator’s Reference)
Or you can create a new domain with appropriate settings and assign the HSM client node to this new domain. By that you will not affect other client nodes, but you will have to maintain one other domain. (See "DEFINE DOMAIN" and "UPDATE NODE" commands in the Tivoli Storage Manager Administrator’s Reference).
You may have to activate your changes with the command "ACTIVATE POLICYSET" (see Tivoli Storage Manager Administrator’s Reference).
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21391244