3 |
Start the local instance with the FORCE NOMOUNT option. |
5 |
Start the local instance with the FORCE NOMOUNT option. |
9 |
On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next. |
10 |
On the Create Selection Set page, navigate to the source NetVault Backup Client and database, select the Whole Database node, and click Edit Plugin Options. |
11 |
Click the Restore Options tab, and select the Check Read-Only Datafiles and Restore if Necessary and Check Read-Only Datafiles and Recover if Not Current options to include read-only datafiles in the restore and recovery process. |
12 |
Because recovery must be performed in a disaster recovery scenario, on the Perform Recovery tab, select Perform Database Point-in-Time Recovery. |
13 |
14 |
17 |
IMPORTANT: After completing a disaster recovery, Quest recommends that you perform a Full or Incremental Level 0 backup with the entire database selected on the NetVault Backup Selections page. |
2 |
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 to request relocation of the RAC Database-Based Plug‑in for Oracle license keys. |
With Plug‑in for Oracle installed on the alternate node, the restore process is similar to performing restores in a single-instance, non-RAC environment except for the following differences:
• |
During the Selecting data for a restore phase of performing RMAN restores, select the backup set from the node on the Create Selection Set page where the Oracle SID equals the Oracle® SID of the instance where the plug-in was originally installed before the relocation. |
• |
During the Setting restore options phase, set the Target Database Authentication Details to the appropriate values for the local instance on the alternate node where the plug-in now 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.
A Duplicate Database backup lets you create a duplicate or clone of a source database for special purposes that must not affect the overall backup and restore procedures for the source database. In a RAC environment, Oracle® does not support duplicating a multi-instance database to a different multi-instance database. However, Oracle does support duplicating a multi-instance database to a single-instance database followed by converting the single-instance database to a multi-instance database. For more information, see the Oracle Real Application Clusters Installation Guide.
PFILE updated with auxiliary values: In addition to the updates to the PFILE as specified in the Non-RAC duplication procedures, the following additional updates must be made when the source database is a multi-instance database:
1 |
• |
<database/instance_name>.cluster_database=TRUE |
• |
<instance_name>.instance_number=N |
• |
<instance_name>.thread = N |
• |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center