Veritas NetBackup™ for Oracle Administrator's Guide
- 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
- About Oracle Intelligent Policies (OIP)
- About script- or template-based Oracle policies
- About adding backup selections to an Oracle policy
- About configuring the run-time environment
- About creating templates and shell scripts
- About creating RMAN scripts manually
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- About NetBackup for Oracle restores
- Using NetBackup for Oracle in a Microsoft Windows cluster environment
- Guided Recovery
- Troubleshooting Guided Recovery
- 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
- Troubleshooting
- Troubleshooting RMAN backup or restore errors
- Appendix A. Real Application Clusters
- Appendix B. Best practices for protecting Oracle RAC with NetBackup
- Appendix C. Deduplication best practices
- Appendix D. Snapshot Client support of SFRAC
- Appendix E. 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 F. XML Archiver
- NetBackup for Oracle XML export and XML import
- About XML export templates and shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- Troubleshooting XML export or XML import errors
- Appendix G. Register authorized locations
Logging the RMAN input and output on a client
NetBackup has the ability to log the RMAN input and output that is logged locally on the client and also sent to the Activity Monitor. The RMAN_OUTPUT_DIR entry specifies which directory to place the RMAN input and output locally on the client for Oracle Intelligent Policy backups. The log is only created when a backup is run using an Oracle Intelligent Policy (OIP) and the file is continuously updated during the RMAN backup. Only one RMAN_OUTPUT_DIR entry per client is allowed in a Windows environment. In a UNIX environment, each user can place the output in a different location by adding the RMAN_OUTPUT_DIR entry to $HOME/bp.conf
file. The value in the $HOME/bp.conf
file takes precedence if it exists. NetBackup does not clean up the log files so the Oracle user has to clean up the log files manually.
You must use the nbgetconfig and the nbsetconfig commands to view, add, or change the option. The directory that is specified must exist and the Oracle user needs to have permission to create files within the directory.
Use the following format:
RMAN_OUTPUT_DIR = directory_name
The directory_name is a directory to which the Oracle user has permission to create files within the directory.
For information about these commands, see the NetBackup Commands Reference Guide.
The file name has a specific format that includes the client name, policy name (OIP), schedule type, date stamp (yyyymmdd), and timestamp (hhmmss). The following is an example of how the file name looks in the directory:
orac121_backuppolicyname_full_20160201_184157_GMT.log
The following are examples of RMAN_OUTPUT_DIR entires:
Windows: install_path\oracle\oracle_logs\RMAN
UNIX: /oracle/oracle_logs/rman