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
Configuring the SFRAC environment for a backup operation
The backup and rollback operations involve the Oracle Agent and the hardware array. The configuration steps required for both of these operations should also be done before taking the snapshot.
The following lists the prerequisites before you perform a backup in the SFRAC environment.
To configure the SFRAC environment for a backup operation
- Configure a virtual IP or virtual name over the cluster. NetBackup refers to the client by using this virtual name.
- The NetBackup client name on each node of the cluster must match the virtual name that is configured on the cluster. Do one of the following:
If you have already installed the client, change the CLIENT_NAME entry in the
bp.conffile of the NetBackup directory to the following:
CLIENT_NAME = <virtual_name>
Alternatively, add the following parameter to the RMAN script file that you are using for backup and restore, and keep the default CLIENT_NAME as the hostname:
NB_ORA_CLIENT = <host_name>
- Specify the required host mode options in the storage array that provides the storage LUNs. For example, in the Host group options of an Hitachi array, enter the type of host (for example, Solaris) and enable the VERITAS Database Edition/Advanced Cluster for Oracle RAC (Solaris) option.
- Add the following line to the
bp.conffile, on each node in the cluster.
PREFERRED_NETWORK = <virtual-host-name>
This entry is required when running a rollback operation.
- If the CFS version that you run does not support group quiescence, enable serial quiescence by adding the following lines to the
- Ensure that the database is in open (read-write) mode.
- Ensure that the service group for the database in VCS is in the online state.
- Because only the master node of the cluster supports the rollback restore, change the virtual IP before a rollback operation so that it points to the master node.
- Configure a snapshot backup policy for the SFRAC environment. In the backup selection tab of the policy, make sure that you provide a path name to the RMAN script. Make sure that the script resides on all the nodes of the cluster. Parameters like ORACLE_SID can differ on each of the nodes. For example, on node 1, the ORACLE_SID can be symc1 and on node 2, the ORACLE_SID can be symc2.