Veritas NetBackup™ for DB2 Administrator's Guide
- Introduction to NetBackup for DB2
- Installing NetBackup for DB2
- Configuring NetBackup for DB2
- About configuring a backup policy for DB2
- About adding backup selections to a DB2 policy
- About backing up archive log files with the user exit program
- Configuring the run-time environment
- Creating a db2.conf file for use with the user exit program
- Creating a db2.conf file (vendor method)
- Configuring bp.conf files in a cluster environment
- About NetBackup for DB2 templates and shell scripts
- Performing backups and restores of DB2
- About user-directed backups
- Performing a database restore
- About an alternate restore
- Using Snapshot Client with NetBackup for DB2
- About NetBackup for DB2 with Snapshot Client operations
- Restoring NetBackup for DB2 from a snapshot backup
- About configuring NetBackup for DB2 block-level incremental backups on UNIX
- Configuring policies for BLI backups with NetBackup for DB2
- About Snapshot Client effects
- Troubleshooting NetBackup for DB2
- About the NetBackup for DB2 log files
- Appendix A. Configuration for a DB2 EEE (DPF) environment
- Appendix B. Using NetBackup for DB2 with SAP®
- Appendix C. Register authorized locations
Restoring and recovering a DB2 database - with a catalog name that has been specified
A catalog name can be specified for a database backup and an archive log backup. If a user specified a catalog name during a backup, there are certain setup actions you must follow during restore operations. Follow the following options for use in a Windows and UNIX environment.
Windows:
If the catalog name is equal to the name of the client performing the restore, no special setup is needed.
If the primary and the client are the same server and if the catalog name does not equal the name of the client performing the restore, update the
db2.conf
as follows:DATABASE and ARCHIVE stanzas:
CLIENT <catalog name>
ARCHIVE stanza only:
FORCE_BACKUP_CLIENT <name of the host performing the restore>
The newer releases of the DB2 database want to perform a backup of the archive logs after a restore.
If the client is a different server than where the backup has occurred and if the catalog name does not equal the name of the client performing the restore:
db2.conf
DATABASE and ARCHIVE stanzas:
CLIENT <catalog name>
ARCHIVE stanza only:
FORCE_BACKUP_CLIENT <name of the host performing the restore>
The newer releases of the DB2 database want to perform a backup of the archive logs after a restore.
The
altnames
directory must be set up:install_path\netbackup\db\altnames
UNIX:
If the catalog name is equal to the name of the client performing the restore, no special setup is needed.
If the catalog name does not equal the client name performing the restore, update the
db2.conf
as follows:db2.conf
DATABASE and ARCHIVE stanzas:
CLIENT <catalog name>
ARCHIVE stanza only:
FORCE_BACKUP_CLIENT <name of the host performing the restore> The newer releases of DB2 want to perform a backup of the archive logs after a restore
The
altnames
directory must be set up:/usr/openv/netbackup/db/altnames
More Information