NetBackup™ Release Notes
- About NetBackup 10.0
- New features, enhancements, and changes
- NetBackup 10.0 new features, changes, and enhancements
- Operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- NetBackup Cloud operational notes
- NetBackup with Veritas CloudPoint operational notes
- NetBackup for NDMP operational notes
- NetBackup for OpenStack operational notes
- NetBackup internationalization and localization operational notes
- NetBackup Snapshot Client operational notes
- NetBackup virtualization operational notes
- Appendix A. About SORT for NetBackup Users
- Appendix B. NetBackup installation requirements
- Appendix C. NetBackup compatibility requirements
- Appendix D. Other NetBackup documentation and related documents
NetBackup for Oracle and NetBackup for DB2 prevent the direct expiration of backup images
Catalog maintenance operations on Oracle and DB2 databases 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_ORACLE_DIRECT_EXPIRE PREVENT_DB2_DIRECT_EXPIRE
In a clustered primary server environment, these settings should be set and match in all the primary server bp.conf
files.
For more information, see the NetBackup for Oracle Administrator's Guide and the NetBackup for DB2 Administrator's Guide.