Configuring the plug-in and adding a database
Configuring Plug‑in for Oracle for a clustered failover environment is almost identical to configuring the plug-in for a single-instance, non-clustered environment. Adding a database involves the following exceptions:
|
• |
Oracle SID: Enter the local SID to the active node in the cluster for the target Oracle® database. The local SID is the Oracle instance name on the local node for the target database. |
|
• |
Control File Autobackup enabled: Quest recommends that you select this option. |
|
• |
PFILE usage: If the local instances in the cluster nodes of the targeted Oracle Database use PFILE instead of SPFILE, you might want to clear the Use RMAN Commands to Backup SPFILE option on the RMAN Details tab. Access this tab through the Add Database or Edit Database options, and enter the applicable information in the Parameter File(s) Path box on the Oracle Instance Details tab. |
For more information, see Configuring the plug-in and Adding a database.
|
IMPORTANT: If a failover to a different node occurs, use the Add Database option to add the Oracle Database information to the plug-in on the active node — the one to which the cluster failed over. You only need to enter this information once; in subsequent failovers, the plug-in automatically retrieves the information. |
Backing up data
Backing up data using Plug‑in for Oracle that has been set up for use in a Virtual Client is relatively 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 in the backup.
Restoring data
Restoring data to a Virtual Client is conducted in the same manner as a restore performed to a traditional NetVault Backup Client. All options available for a restore with Plug‑in for Oracle are also available for Failover Clustering environments, and data selection is also performed in the same way. The difference is that restorable backups of a Virtual Client are displayed on the Create Selection Set page under the name of the Virtual Client, not the specific NetVault Backup Client or node that was active during each backup. When a restore job is initiated, NetVault Backup communicates with all member Clients to determine which machine is in control of the failover cluster, and targets this machine for the restore.
|
IMPORTANT: The Restore Backup taken from NetVault Backup Client field on the Configure dialog box must contain the name of the NetVault Virtual Client that performed the backup; otherwise, restores fail. For more information on using the Configure dialog box, see Configuring the plug-in.
To restore a Controlfile Autobackup or a backup taken from CLI in failover cluster environment, provide the name of the NetVault Physical Client either in option Restore Backup taken from NetVault Backup Client or in the option NV_ORIGINAL_NV_CLIENT (use this variable with “send”). The Oracle RMAN backup pieces are stored in the NetVault Backup Media Manager, under the name of the NetVault Client that performed the backup. The Client name is listed in the Create Restore Job - Choose Saveset page, in the Saveset Information area. |
All the instructions offered about performing a restore can be used in the recovery of a Virtual Client. For more information on restoring a NetVault Backup Virtual Client, see the various topics in Restoring data.