Veritas NetBackup™ for Oracle Administrator's Guide
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Linking Oracle RMAN with NetBackup on UNIX platforms
- 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
- Redirecting a restore to a different client
- 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 NetBackup for Oracle restores of volumes and file systems using snapshot rollback
- About configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- 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
- About redirecting a restore of an XML export archive to a different client
- Troubleshooting XML export or XML import errors
- Appendix G. 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 the NetBackup for Oracle Template Wizard or in the RMAN script. A few can be set in multiple places, most notably those that specify the master 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.
The template fields for Client name and Schedule name, if specified in the backup template.
The template fields for Server name and Backup policy name, if specified in the backup template and initiated from the client.
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 bpdbsboraor RMAN is started.
The environment variables that the login or shell inherits.
The environment variables that the master server initiation of an automatic schedule sets.
On UNIX, the Oracle user's configuration file;
The NetBackup configuration:
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 master server selects the first policy of type Oracle for the client name.
The master server selects the first schedule of type Application Backup (stream-based) or Automatic Full Backup (proxy) from the policy.
The Server name and Backup policy name that is configured within a backup template are only used when initiated from the client.
If the backup is initiated from an automatic schedule on the master server the operation is different. The backup uses the name of the master server and policy that was used to initiate the template. This operation allows a template to be used with multiple policies, with different automatic schedules, and even different master servers.