The NetVault Plug-in for Oracle provides support for Oracle Server Failover Clustering. Using the failover cluster network name, the plug-in is able to identify the current node that is in control of the Oracle Server Clustered Service and target it for backup. In NetVault terminology, a clustered service is accessed by a Virtual Client. The references to Virtual Client in Plug-in for Oracle are basically references to the Clustered Service in the Oracle Server Failover Cluster environment.
Sure this may sound confusing so why not just backup the files to a .bak file and send it to disk or tape for storage. This is just not ideal when it comes to a clustered environment with potentially many nodes with one or more shared disks. Various resources hosted by the nodes, such as IP, shared storage, and an application – Oracle in this case – can be grouped to a created Clustered Service.
So let’s try to take the mystery out of setting up the NetVault plug-in in a Failover Cluster environment vs. a traditional one. The link provided above is for additional reference.
a. You must have a properly configured Oracle Cluster environment.
b. The NetVault backup server must be properly configured and must sit outside the Oracle Server cluster. The NetVault backup server must have network connectivity to the nodes (hosts) within the cluster.
c. The installation of the plug-in for a clustered environment is different than the traditional plug-in install. This process is completed through the creation of a Virtual Client on the NetVault backup server. A Virtual Client is basically a group of nodes within the cluster that are seen by the NetVault backup server as a single client that is created to back up a single clustered service.
d. Creating a Virtual Client is quite simple. Click Manage Clients, click Add Virtual Client to display this screen. Assign a name to the Virtual Client (Quest recommends using the virtual-network name that was assigned to the Oracle Database). Lastly select the hosts that are to be included in the creation of the Virtual Client. After the creation the plug-in is transferred to all designated cluster nodes and installed locally.
2. Licensing the plug-in.
a. The plug-in is licensed differently for an Oracle clustered environment. The plug-in supports backup and restore of shared data only. Hence, for an Oracle Database Server Failover cluster environment, only a single license would be needed – a clustered application license for the Virtual Client.
3. Configuring the plug-in for Oracle for a clustered environment is almost identical to configuring the plug-in for a single-instance, non-clustered environment.
a. Oracle SID: Active node in the cluster
b. Control File Autobackup enabled: Recommended
c. PFILE or SPFILE: See Oracle RMAN differences
4. Backing up Data.
a. Selecting data for backup once the plug-in for Oracle has been setup is relatively quite simple. On the NetVault Backup Selections page, open the Virtual Client node, open plug-in for Oracle, and select the Oracle Server Instances, or the items contained within for inclusion for backup.
5. Restoring Data.
a. Restoring data to a Virtual Client is really no different than restoring data to a NetVault client, with a few exceptions. Restoring backups of a Virtual Client are displayed on the Create Selection Set page under the name of the Virtual Client. When a restore job is initiated, NetVault communicates with all the hosts within the cluster to determine which machine is in control of the failover cluster, and targets this machine for restore. For additional information regarding restore:
NetVault Release Notes