NetBackup™ for DB2 Administrator's Guide
- Introduction to NetBackup for DB2
- Installing NetBackup for DB2
- Configuring NetBackup for DB2
- Overview of NetBackup for DB2 configuration
- About permissions for NetBackup for DB2 log files (UNIX)
- About configuring a backup policy for DB2
- About adding backup selections to a DB2 policy
- Configuring an application backup schedule
- Example application backup schedule
- Configuring automatic backup schedules
- Example automatic backup schedule
- About schedule properties
- NetBackup for DB2 backup types
- Performing a manual backup
- Reviewing the auto-discovered mappings in Host Management
- 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
- Keywords for the db2.conf file
- NetBackup for DB2 environment variables
- Configuring the logon account for the NetBackup Client Service for NetBackup for DB2
- About NetBackup for DB2 shell scripts
- Performing backups and restores of DB2
- Using Snapshot Client with NetBackup for DB2
- NetBackup for DB2 with Snapshot Client features
- About NetBackup for DB2 with Snapshot Client operations
- About the sequence of a NetBackup for DB2 backup operation with Snapshot Client methods
- About the sequence of a NetBackup for DB2 restore operation with Snapshot Client methods
- About database objects supported by advanced backup methods
- About multistreaming and DB2 snapshot backups
- About symbolic links and DB2 backups and restores (UNIX)
- NetBackup for DB2 stream-based operations
- NetBackup for DB2 file-based operations
- Example: multiple sessions for a DB2 snapshot backup
- About configuring Snapshot Client with NetBackup for DB2
- Configuration requirements for snapshot backups with NetBackup for DB2
- Configuring a snapshot policy for NetBackup for DB2
- About configuring the db2.conf for a snapshot policy
- Restoring NetBackup for DB2 from a snapshot backup
- About restoring individual files from a NetBackup for DB2 snapshot backup
- About NetBackup for DB2 restores of volumes and file systems using snapshot rollback
- Performing a NetBackup for DB2 point-in-time rollback restore from a SnapVault backup (UNIX)
- Performing a snapshot rollback restore from the command line
- Troubleshooting NetBackup for DB2 rollback restores
- About configuring NetBackup for DB2 block-level incremental backups on UNIX
- How BLI works with NetBackup for DB2 (UNIX)
- About the Storage Checkpoint facility and NetBackup for DB2
- Configuration requirements for BLI backups with NetBackup for DB2
- Storage Checkpoint configuration on the NetBackup for DB2 client
- Configuring policies for BLI backups with NetBackup for DB2
- BLI incremental backup options using NetBackup for DB2
- About Snapshot Client effects
- Performing NetBackup for DB2 backups with Snapshot Client methods
- Performing NetBackup for DB2 restores with Snapshot Client methods
- Troubleshooting NetBackup for DB2
- NetBackup debug logs and reports
- Enabling the debug logs for a NetBackup for DB2 client automatically (Windows)
- Enabling the debug logs manually (Windows)
- Enabling the debug logs manually (UNIX)
- About the NetBackup for DB2 log files
- Setting the debug level on a Windows client
- Setting the debug level on a UNIX client
- Minimizing timeout failures on large database restores
- Minimizing the loading and unloading of tapes for database backups
- Use the NET_BUFFER_SZ file to speed up a slow restore
- About false restore failures reported in the activity monitor
- About the error message codes
- 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.
If you use a non-root service user account, specific access must be allowed for that user when you add files to the /usr/openv/netbackup/db/altnames directory. The service user account must have full access to these files through the ownership or group and the permissions. For example, if the service user is svcname and its group is srvgrp, the file can have permissions of 400. If the file owner is for a different user and group, the file permissions must allow access to the service user. For example, 777. Equivalent permission settings must be used in a Windows 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.confas 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.confDATABASE 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
altnamesdirectory 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.confas follows:db2.confDATABASE 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
altnamesdirectory must be set up:/usr/openv/netbackup/db/altnames
More Information