NetBackup™ for Oracle Administrator's Guide
- Introduction
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Configuring RBAC for the Oracle administrator
- Managing Oracle instances and databases
- Managing Oracle credentials
- Configuring Oracle policies
- Preparing for NetBackup for Oracle configuration
- About Oracle Intelligent Policies (OIP)
- About script-based Oracle policies
- Managing Oracle RAC
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- Managing expired backup images
- About NetBackup for Oracle restores
- Using NetBackup for Oracle in a Windows Server Failover Cluster (WSFC)
- Oracle cloning
- NetBackup Copilot for Oracle
- Configuring an OIP using universal shares (Oracle Copilot)
- Oracle Copilot with instant access
- Prerequisites when you configure an instant access Oracle database
- NetBackup for Oracle with Snapshot Client
- About NetBackup for Oracle with Snapshot Client
- How NetBackup for Oracle with Snapshot Client works
- About configuring Snapshot Client with NetBackup for Oracle
- Restoring NetBackup for Oracle from a snapshot backup
- About configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- NetBackup Dedupe Direct for Oracle
- Using NetBackup Dedupe Direct for Oracle plug-in
- Other Oracle configuration
- Troubleshooting
- Troubleshooting RMAN backup or restore errors
- Appendix A. Deduplication best practices
- Appendix B. Snapshot Client support of SFRAC
- Appendix C. Script-based Block-Level Incremental (BLI) Backups without RMAN on UNIX and Linux systems
- Verifying installation requirements for BLI backups without RMAN
- Creating NetBackup policies for script-based BLI backup
- Creating notify scripts for BLI backups
- Performing backups and restores
- About troubleshooting backup or restore errors
- Appendix D. XML Archiver
- NetBackup for Oracle XML export and XML import
- About XML export shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- Troubleshooting XML export or XML import errors
- Appendix E. Register authorized locations
About preventing the direct expiration of backup images
Catalog maintenance operations on Oracle 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 | 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 dbclient
log message for Oracle:
Image is on LEGAL HOLD - Failed to remove, %s, from image catalog.