Before the DB2® database manager can use an IBM® Tivoli® Storage Manager (TSM) client to manage database or table space backup or restore operations, you must configure the TSM environment.
A functioning TSM client and server must be installed and configured. In addition, the TSM client API must be installed on each DB2 database server. TSM client proxy nodes are supported if the TSM server has been configured to support them. For information on server configuration and proxy node support, see Considerations for using Tivoli Storage Manager or refer to the Tivoli documentation.
To configure the TSM environment for use by DB2 database systems:
Depending on your backup and log archiving strategies, you might need to perform additional steps to configure the TSM clients if you want to use proxy nodes. Proxy nodes enable you to consolidate backups and log archives of databases existing on multiple client nodes or under multiple users to a common target nodename on the TSM server. This configuration is useful when the administrator or computer that performs the backup can change over time, such as with clusters. The asnodename option also allows data to be restored from a different computer or from a user different than the one that performed the backup.
If you want to use TSM in your DB2 pureScale® environment, proxy node configurations are recommended because each member can be represented as a TSM client or node and be mapped to a common proxy node.
If you do not want to use proxy nodes by default, no additional client setup is required. When you want to perform backup or restore operations using proxy nodes, specify the asnodename value in the OPTIONS parameter when invoking the BACKUP DATABASE or RESTORE DATABASE commands.
You can set one or more of the following database configuration parameters to enable different proxy node settings for each database:
db2 update db cfg for dbname using vendoropt "'-asnodename=proxynode'"
where proxynode
is the name of the shared TSM proxy node.db2 update db cfg for dbname using logarchmeth1 tsm
logarchopt1 "'-asnodename=proxynode'"
where proxynode is
the name of the shared TSM proxy node.You can make similar updates to the logarchmeth2 and logarchopt2 database configuration parameters.
In DB2 pureScale environments, these database configuration parameters are global parameters and you can set them from any member.
asnodename proxynode
where proxynode is
the name of the shared TSM proxy node. servername servername
where servername is
the TSM server name.