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 shell scripts
- Performing backups and restores of DB2
- 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
About preventing the direct expiration of backup images
Catalog maintenance operations on DB2 send requests into NetBackup to synchronize the database catalog with the NetBackup catalog. As part of the catalog synchronization, the database may initiate an image expiration (delete) request to the NetBackup catalog. These requests may also come from the DBA when command-line options are used. For compliance reasons, you may want to prevent the expiration of images in the NetBackup catalog from a database request by using a bp.conf
entry on the primary server.
To prevent the expiration of backup images, use the following bp.conf
entry on the primary server:
PREVENT_DB2_DIRECT_EXPIRE | YES: This setting prevents the image delete requests from the database. The delete request receives a status code of 1420 and the log message indicates that the image is on NO: The default setting. All image delete requests are honored from the database. |
Note:
The normal image expiration (retention) and the bpexpdate command are unaffected by this setting.
In a clustered primary server environment, these settings should be set and match in all the primary server bp.conf
files.
The following is an example of a log entry when a status code of 1420 is produced.
The bpdb2
log message for DB2:
Unable to process delete request. Image is on LEGAL HOLD