Please enter search query.
Search <book_title>...
NetBackup™ for Oracle Administrator's Guide
Last Published:
2023-10-23
Product(s):
NetBackup (10.3.0.1, 10.3)
- 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
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.conf
file 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.conf
file, 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
/usr/openv/lib/vxfi/configfiles/vxfsfi.conf
file.[QUIESCENCE_INFO] "QUIESCENCE_SERIAL_QUIESCENCE"=dword:00000001
- 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 primary node of the cluster supports the rollback restore, change the virtual IP before a rollback operation so that it points to the primary 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.