Please enter search query.
Search <book_title>...
NetBackup™ for Oracle Administrator's Guide
Last Published:
2022-10-28
Product(s):
NetBackup & Alta Data Protection (10.1)
- Introduction
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Oracle policy configuration
- Preparing for NetBackup for Oracle configuration
- Instance management for an Oracle Intelligent Policy (OIP)
- About Oracle Intelligent Policies (OIP)
- About script-based Oracle policies
- 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 Microsoft Windows cluster environment
- 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
- 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
To prevent the expiration of backup images, use the following bp.conf
entry on the primary server:
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.