NetVault Plug-in for Oracle 12.2

Adding a multi-instance database in Plug‑in for Oracle is almost identical to adding a single-instance, non-RAC database except for the following differences:

•

Oracle SID: Enter the local SID for the target RAC database. The local SID is the instance name for the target RAC database on the node where the plug-in is installed.

•

Parameter File(s) Path: In a multi-instance RAC environment, the plug-in requires the usage of an SPFILE as a dynamic method of maintaining initialization parameters. The SPFILE must be stored on the shared storage in ASM. Because the SPFILE is included in the Control File Autobackups, this field should be left blank in a RAC environment.

•

Control File Autobackup enabled: Select this option because Control File Autobackups are required in a RAC environment.

For more information, see Configuring the plug-in.

Backing up data

RMAN-based backups are the only supported backup method for multi-instance RAC databases. RMAN is RAC-aware in that it automatically identifies that a database is a multi-instance RAC database and backs up the selected data accordingly.

With the plug-in installed on one of the nodes that hosts one of the instances for the RAC-enabled database, all RMAN-based backups and restores are performed from this single installation of the plug-in.

The Parameter File node is not selectable on the NetVault Backup Selection page.

For more information on selecting data for backup, setting backup options, and finalizing and submitting the job, see Performing RMAN backups.

Performing backups after node failure

If the node where the plug-in is installed in the RAC environment experiences a node failure and the node is, or will be, unavailable at the time of the next scheduled backup, relocate the plug-in to an alternate node in the RAC environment.

Install the NetVault Backup Client software on an alternate node.

Install the NetVault Backup Client on an alternate node in the RAC environment. During the installation process, be sure to use the same NetVault Machine Name that was used during the installation of the NetVault Backup Client on the original node. For example, if PROD_RAC was the NetVault Machine Name specified during the installation on the original node, PROD_RAC should be used as the NetVault Machine Name on the alternate node.

Install Plug‑in for Oracle.

After the NetVault Backup Client has been installed on the selected node of the RAC environment, install the plug-in. The process is identical to installing the plug-in for a single-instance, non-RAC environment except that plug-in is installed on the NetVault Backup Client that corresponds with the generic or virtual name provided as the NetVault Machine Name during the NetVault Backup Client installation.


	IMPORTANT: If the relocation of the plug-in is expected to be permanent or last longer than 45 days, visit https://support.quest.com/contact-us/licensing and request relocation of the RAC Database-Based Plug‑in for Oracle license keys.

With the plug-in installed on the alternate node, update the Oracle SID field on the Edit Oracle Database dialog box.

Enter the local SID for the target RAC database. The local SID is the instance name for the target RAC database on the node where the plug-in has been relocated. For more information, see Editing database information.

For more information on selecting data for backup, setting backup options, and finalizing and submitting the job, see Performing RMAN backups.

Restoring data in a RAC environment

Because RMAN is RAC-aware, it restores the selected data accordingly. With Plug‑in for Oracle installed on one of the nodes that hosts one of the instances for the RAC-enabled database, all RMAN-based restores are performed from this single installation of the plug-in. The restore process is similar to restoring single-instance, non-RAC environments, with the following exceptions:

•

During the Selecting data for a restore phase of performing RMAN restores, you might select a backup set from a node where the Oracle SID equals the Oracle SID of the instance on which the plug-in is running. But you might also select a backup set from an Oracle SID of a different RAC node for which backups were performed previously. For more information about performing restores after a node failure, see Performing restores after node failure.

•

During the Setting restore options phase, if authentication for the target database is needed, set the Target Database Authentication Details to the applicable values for the local Oracle instance on which the plug-in that is performing the restore resides. For more information, see Setting Destination Details.

For more information on preparing the database for recovery, selecting data items for a restore, setting restore options, finalizing and submitting the job, and opening the database for use, see Performing RMAN restores.


	IMPORTANT: If the plug-in was relocated to an alternate node and backups were performed from multiple instances, use the current Oracle SID when selecting data on the Create Selection Set page.

The following topics outline additional types of RMAN recovery that are available in a RAC environment.

•

Recovering a Whole Database to the same RAC environment

•

Restoring SPFILE in a RAC environment

•

Restoring Control Files in a RAC environment

•

Performing disaster recovery in a RAC environment

•

Performing restores after node failure

•