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 virtual names and NetBackup for Oracle
Users of a RAC can typically access the database by a virtual network host name. This access is dependent on the configuration of a RAC and any cluster software on which it is running.
The virtual network host name may be associated with an IP address in the following ways:
With an IP address for a host in the cluster
A virtual IP address for an Oracle database instance running on a host in the cluster
A failover virtual IP address that may move between the hosts in the cluster
Backup operations may use the various virtual network host names, or the network host name of the hosts in the cluster.
To differentiate between the various network names, the following terms and definitions are used:
The network host name that is associated with a specific host in the cluster.
The network host name that is associated with a virtual IP address specific to an instance in the cluster.
The network host name that is associated with an IP address that is active on a running node. This network host name is the network host name that can perform a backup at this time.
Do not use a single client name if the backup is load balanced across more than one node. In a load-balanced configuration, the node that hosts the IP address to which the client name resolves, generates successful backups. However, the jobs originating from the other nodes fail with status code 54.
Oracle 11g R2 Grid Infrastructure (CRS) includes the Single Client Access Name (SCAN) feature. A single SCAN can resolve to multiple IP addresses each assigned to a different physical node in the cluster.
A SCAN can be used in a NetBackup policy that receives the Application Backup request. However, this abstraction of the client name causes backup and restore jobs to fail with status code 54. Also, the client side fails with status code 6 (backup) or status code 5 (restore).
Accordingly, ensure that the client that appears in the NetBackup Oracle policy is not a SCAN. Also, ensure that any NB_ORA_CLIENT or CLIENT_NAME that the node provides in the backup request is not a SCAN. These names must reliably resolve on both the master server and the media server to an IP address. This IP address allows the server processes to connect to the node from which the backup request originated.