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.
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.
2 |
Install Plug‑in for Oracle. |
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. |
3 |
With the plug-in installed on the alternate node, update the Oracle SID field on the Edit Oracle Database dialog box. |
For more information on selecting data for backup, setting backup options, and finalizing and submitting the job, see Performing RMAN backups.
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center