DB2 10.5 for Linux, UNIX, and Windows

Considerations for using Tivoli Storage Manager

You can use Tivoli® Storage Manager to create backup images of a DB2® database. When you are deciding which backup tool to use for your database, you must consider the features and restrictions of each available option.

To use specific features within Tivoli Storage Manager (TSM), you might be required to give the fully qualified path name of the object using the feature. (Remember that on Windows operating systems, the \ will be used instead of /.) The fully qualified path name of:
- A full database recovery object is: /database/DBPARTnnn/FULL_BACKUP.timestamp.seq_no
- An incremental database recovery object is: /database/DBPARTnnn/DB_INCR_BACKUP.timestamp.seq_no
- An incremental delta database recovery object is: /database/DBPARTnnn/DB_DELTA_BACKUP.timestamp.seq_no
- A full table space recovery object is: /database/DBPARTnnn/TSP_BACKUP.timestamp.seq_no
- An incremental table space recovery object is: /database/DBPARTnnn/TSP_INCR_BACKUP.timestamp.seq_no
- An incremental delta table space recovery object is: /database/DBPARTnnn/TSP_DELTA_BACKUP.timestamp.seq_no
where database is the database alias name, and DBPARTnnn is the database partition number. The names shown in uppercase characters must be entered as shown.
In the case where you have multiple backup images using the same database alias name, the time stamp and sequence number become the distinguishing part of a fully qualified name. You will need to query TSM to determine which backup version to use.
If you perform an online backup operation and specify the USE TSM option and the INCLUDE LOGS option, a deadlock can occur if the two processes try to write to the same tape drive at the same time. If you are using a tape drive as a storage device for logs and backup images, you need to define two separate tape pools for TSM, one for the backup image and one for the archived logs.
To use client proxy nodes, the TSM administrator must complete the following steps on the TSM server:
1. If the DB2 clients are not already registered with the TSM server, register each client using the register node TSM command.
2. Register a (virtual) common TSM nodename to be used by the group of clients with the TSM server using the register node TSM command.
3. Grant proxy authority to all computers in the group using the grant proxynode TSM command.
For information on how to set up proxy node clients, see Configuring a Tivoli Storage Manager client or refer to the Tivoli documentation.
When taking incremental backups where only a small number of pages have been modified, it might be necessary to increase the TSM parameter IDLETIMEOUT to be larger than the time it takes to complete the backup of the largest tablespace. This prevents TSM from closing the session prior to the completion of the incremental backup.