Backup commands for DB2 databases

When you are backing up DB2® databases, use specific commands for your database configuration and backup type.

The following table summarizes the commands that are needed for backing up DB2 databases for different database configurations and corresponding backup types.

Table 1. Summary of backup commands for DB2 databases
Database configuration	Snapshot backup (disk only)	Back up to Tivoli® Storage Manager
Database configuration	Snapshot backup (disk only)	From production database (tape only)	Integrated with snapshot	From existing snapshot
DB2	db2 backup ... use snapshot ...	db2 backup ... use tsm	db2 backup ... use snapshot ... ¹	fcmcli -f tape_backup ²
DB2 in an SAP environment	db2 backup ... use snapshot ...	db2 backup ... load <library> or backom	db2 backup ... use snapshot ... ¹	fcmcli -f tape_backup²
Note: The profile parameter TSM_BACKUP is set to YES, MANDATE, or LATEST, and the offload agent (fcmcli) is running in daemon mode on the production server. The profile parameter TSM_BACKUP is set to YES, MANDATE, or LATEST, and the offload agent (fcmcli) is not running in daemon mode.

The db2 backup database command with the use snapshot option is described in the DB2 Command Reference guide.

When you restore a backup image, the whole backup image is restored. Therefore, any data on the file system that is updated or created after the backup is taken is overwritten. To ensure that nothing is overwritten unintentionally, do not store any other data in the data and log volume groups. Any other data that is stored on the volume groups is processed by Tivoli Storage FlashCopy® Manager and included in the backup image.

For DB2 pureScale®, any additional files that are stored in log file sets and data file sets are included in the backup. When you restore a backup image, extra files and nested file sets are overwritten. To avoid overwriting, do not store any other files in log file sets or database data file sets. Ensure that you do not link independent file sets containing unrelated data in file sets that participate in snapshots.

Extra files that are not associated with the database backup operation but are stored in the volume groups can cause the backup to fail. Use the NEGATIVE_LIST parameter in the Tivoli Storage FlashCopy Manager profile to control the processing of these files. For information about this parameter, see the CLIENT profile section for details.

You can start a backup operation from any member of the DB2 pureScale instance. The Tivoli Storage FlashCopy Manager management agent acsd coordinates the backups and communicates between the application and device agents. The management agent is started automatically after the installation. If you are required to start the agent manually, this agent must not be started on more than one member. DB2 pureScale database is regarded as a single partitioned database.