• No results found

Management class to which to bind object

Partitioned Database

Chapter 4. Tivoli Storage Manager server considerations

4.3 Tivoli Storage Manager data objects

4.3.3 Management class to which to bind object

Every data object is bound to a management class when it is first sent to the Tivoli Storage Manager server. The management class determines how the object will be managed on the Tivoli Storage Manager server. A management class is one of the structures that is used in Tivoli Storage Manager policy management. We will not cover all details of Tivoli Storage Manager policy management in this book — only what is needed for backing up DB2 databases to Tivoli Storage Manager.

For a given node, the following can be said: every node belongs to one and only one Tivoli Storage Manager policy domain. The domain a node belongs to can be viewed with the Tivoli Storage Manager administrative command query node <nodename>. Replace <nodename> with the appropriate nodename.

The output of that command for our node JAMAICA_DB2 shows that it belongs to the API_DOMAIN.

Each domain contains one and only one ACTIVE policyset. The active policyset has one default management class. The active policyset represents what policyset is currently in use. The default management class represents which management class will be used if a Tivoli Storage Manager client does not use a specific one, or if the Tivoli Storage Manager client specifies a management class that does not exist in the active policyset for the domain that the node belongs to. The active policyset for a domain and the default management class can be viewed with the command query policy <domain>

active. Replace <domain> with the appropriate domain. The output of that

command for our API_DOMAIN shows that the default management class for nodes in the domain API_DOMAIN is API_MGMTCLASS.

tsm: BRAZIL>q policyset api_domain active

The active policyset for a domain can contain more than one management class. Only one can be the default management class. All management classes for the active policyset can be viewed with the command query mgmtclass <domain> active. Replace domain with the appropriate domain name. The output of that command from our API_DOMAIN shows that there are two management classes in the active policyset for the domain

API_DOMAIN. These classes are API_LONGER and API_MGMTCLASS with API_MGMTCLASS being the default management class.

Policy Policy Mgmt Default Description

Each management class can contain one archive copygroup and one backup copygroup. The copygroup is the final structure in the Tivoli Storage Manager policy management scheme and contains the most important information.

The copygroup is where you specify where the initial destination storage pool of the data object should be. You also specify how the life cycle of the data object is to be managed. The life cycle concept will be covered in the next section. The life cycle is the term used in this book to describe how long a data object (backup or archive) resides on Tivoli Storage Manager storage before being purged.

The retention settings for a backup copygroup can be viewed with the command query copygroup <domain> active <mgmtclass>. Replace <domain>

and <mgmtclass> with the appropriate values for your configuration. The output of that command for our default management class API_MGMTCLASS

in the domain API_DOMAIN shows the retention settings for the backup

To see the initial destination storage pool for this copygroup, you have to use the format=detailed option. Each of the query commands can be used with the additional parameter format=detailed to obtain additional information. The same command used previously to view the backup copygroup plus the format=detailed option shows that the initial destination (COPY

DESTINATION) is the API_DISK_B storage pool.

tsm: BRAZIL>q copygroup api_domain active api_mgmtclass format=detailed Policy Domain Name: API_DOMAIN

To see the retention settings for an archive copygroup, you add the option type=archive to the query copygroup command query copygroup <domain>

active <mgmtclass> type=archive. Replace <domain> and <mgmtclass> with the appropriate values for your configuration. The output of that command for our default management class API_MGMTCLASS in the domain

API_DOMAIN shows the retention settings for the archive copygroup.

tsm: BRAZIL>q copygroup api_domain active api_mgmtclass type=archive

To see the initial destination storage pool for this copygroup, you have to use the format=detailed option again. The same command used previously to view the archive copygroup plus the format=detailed option shows that the initial destination (COPY DESTINATION) is the API_DISK_A storage pool.

tsm: BRAZIL>q copygroup api_domain active api_mgmtclass type=archive format=detailed Policy Domain Name: API_DOMAIN

To summarize the information presented in this section with regards to data objects:

• Every archive data object sent to the Tivoli Storage Manager server is associated with an archive copygroup that determines the initial destination storage pool and how long the archive data object should reside on Tivoli Storage Manager storage.

• Every backup data object sent by the Tivoli Storage Manager server is associated with a backup copygroup that determines the initial destination storage pool and how long the backup data object should reside on Tivoli Storage Manager storage.

• For the archive or backup data object, the copygroup comes from the management class to which the object is bound. The management class that is used to bind comes from the active policyset for the domain of the node that sent the data object. The management class used will either be

the default management class for the active policyset or one specified by the Tivoli Storage Manager client.

• Once the object is sent to the Tivoli Storage Manager server you can verify which management class was used by performing a SQL query of the archives or backups Tivoli Storage Manager internal database table.