TSM abstracts the details of storage devices into a logical construct that requires few API calls. It allows client applications like Backup Server to use TSM API calls.
TSM uses these hierarchical constructs to structure backup data. Typically, you can use the default values supplied by TSM. Default values can be changed only by the TSM administrator at the TSM server; they cannot be changed from Backup Server.
In descending order, the constructs are:
Policy domain – the base element of the logical structure, the policy domain associates a TSM client (a node) with a policy set.
Policy set – each policy domain has one active policy set that determines how TSM server handles data from the TSM clients belonging to the policy domain. Each policy set contains a default management class and one or more additional management classes.
Management class – backup copy groups that contain information about expiration or retention policies for backup objects.
Copy group – defines the expiration or retention policies, such as event-based retention, for backup objects.
If Adaptive Server backups require special expiration
policies, or do not use the default copy groups, the TSM administrator
can create custom classes or groups on the TSM server. You cannot
create these special management classes and copy groups from Backup
Server.
