Veritas NetBackup™ for DB2 Administrator's Guide
- Introduction to NetBackup for DB2
- Installing NetBackup for DB2
- Verifying the operating system and platform compatibility
- About log archiving
- 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
- Creating DB2 scripts manually
- 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
Configuration requirements for snapshot backups with NetBackup for DB2
Each snapshot type has its own hardware requirements, software requirements, compatibility with certain features, and the snapshot methods that are supported. Special requirements apply for specific types of backups. See the NetBackup Snapshot Client Administrator's Guide and the Veritas Support website for more information. Familiarize yourself with this information before you configure any snapshot backups.
The following list highlights some of the requirements that pertain to database agents:
Snapshot Client backups do not back up all database objects. Your backup configuration must include schedules to perform snapshot and stream-based backups. This configuration ensures that the entire database can be restored successfully.
On UNIX, the user identification and group identification numbers (UIDs and GIDs) associated with the files to be backed up must be available. The UID and GID must be available to both the primary client and the alternate backup client. The UID on the primary client and the alternate backup client must be the same. Similarly, the GID on the primary client and the alternate backup client must be the same.
Ensure that the data files reside on a volume or a file system that does not contain archive logs, control files, or executables.
Allocate a different set of volumes or file systems to the DB2 executables versus the configuration files and transaction logs.
One reason to have two different volumes is to separate the data files from the other files. If the logs are configured on the same volumes as the data files, the volumes the logs are temporarily frozen while NetBackup takes the snapshot. The logs and the database activity may freeze until the logs become accessible again.
Another reason for writing the data files to their own repository is because it is required for an instant recovery point-in-time rollback. Only data files can exist on the volume that you want to restore.
The hardware and software that is required for the appropriate snapshot method must be installed and configured correctly.
NetBackup Snapshot Client must be installed and configured correctly, and the master server must have a valid license for this option.
To perform off-host backups, specify the off-host in the backup policy and ensure that host has the software and permissions to mount the snapshot.