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 configuring the run-time environment
When the Oracle Intelligent Policy is not used, there are many user configurable variables that can affect the operation of NetBackup for Oracle. Most can be set only in an RMAN script. A few can be set in multiple places, most notably those that specify the primary server, client name, policy, and schedule.
When these variables are configured in multiple places, the following order of precedence is used (the list is ranked highest to lowest):
RMAN SEND command variables, if specified in the backup script.
RMAN ENV parameter variables, if specified in the backup script.
Environment variables that are inherited from the Oracle listener process startup environment, if RMAN connects to the database using TNS SQL*Net.
Environment variables that are set in the backup script before RMAN is started.
The environment variables that the login or shell inherits.
The environment variables that the primary server initiation of an automatic schedule sets.
On UNIX, the Oracle user's configuration file;
$HOME/bp.conf
.The NetBackup configuration:
Windows: The
HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config
registry keys.UNIX: The
/usr/openv/netbackup/bp.conf
file.Both: The NetBackup GUI settings for server, client name, optional default policy, and optional default schedule.
The following defaults apply:
A server must be specified, there is no default.
The client name defaults to the host name.
The primary server selects the first policy of type Oracle for the client name.
The primary server selects the first schedule of type Application Backup (stream-based) or Automatic Full Backup (proxy) from the policy.