NetVault Plug-in for Oracle 12.2

Oracle RAC environment in place: You must have a properly configured Oracle RAC environment that matches the configuration as specified Performing User Managed backups. In addition, the same version of the Oracle database software must be installed in the RAC environment as it existed on the damaged RAC environment. The ORACLE_HOME should be identical on both the original and new node. You do not have to create the database, but you do need to configure Oracle Net Services and ASM for shared storage.

•

NetVault Backup software and the Plug‑in for Oracle installed: The same version of NetVault Backup software and the plug-in must be installed on one of the nodes in the RAC using the same NetVault Machine Name as previously defined for the RAC environment. Ensure that the plug-in default attributes are defined as specified in Configuring default attributes.

•

DBID of the source database identified: Identify the DBID of the damaged database. If the DBID was not recorded as part of the initial plug-in installation, you can obtain the DBID by examining the NetVault Backup binary logs for RMAN-based backups of the source database. The DBID is also available on the Details dialog box or the Backup Contents tab.

•

Default Location for SPFILE must exist: The default location in the ASM shared storage must exist before performing the following steps. Failure to ensure that the default location exists results in an ORA-17502 Failed to create file error during the SPFILE restore. Additionally, the SPFILE location should be detailed in the PFILE with the SPFILE parameter.

•

Backups of all tablespaces made available: Verify that you have the latest backups of all the tablespaces.

Performing the disaster recovery

Start RMAN, and connect to the target database.

> rman TARGET /

Set the database identifier for the target database with SET DBID.

RMAN displays the DBID whenever you connect to the target. You can also obtain it by inspecting saved RMAN log files, querying the Catalog, or looking at the filenames of Control File Autobackup. The DBID is also available on the Details dialog box or the Backup Contents tab.

SET DBID <DBID>;

Start the local instance with the FORCE NOMOUNT option.

STARTUP FORCE NOMOUNT;

Restore the SPFILE Autobackup.

If you are restoring the SPFILE to the default location, run:

RUN {

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

RESTORE SPFILE FROM AUTOBACKUP;
}

Start the local instance with the FORCE NOMOUNT option.

STARTUP FORCE NOMOUNT;

Restore the Control File Autobackup.

If you are restoring the Control File from the last Autobackup, run:

RUN {

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

RESTORE CONTROLFILE FROM AUTOBACKUP;

}

Mount the database:

ALTER DATABASE MOUNT;

Disable Block Change Tracking.

SQL "ALTER DATABASE DISABLE BLOCK CHANGE TRACKING";

On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next.

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.

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.

Because recovery must be performed in a disaster recovery scenario, on the Perform Recovery tab, select Perform Database Point-in-Time Recovery.

PIT Recovery recovers the database to a specific time, log sequence number, or SCN. If the specific time or log sequence of the failure is not known, Quest recommends that you use the SCN option.

On the Recovery Catalog tab, clear the Use Catalog option.

Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.

RMAN automatically chooses the best available full, incremental, or Archived Log backups and restores and recovers the database.

In RMAN, enable Block Change Tracking.

SQL "ALTER DATABASE ENABLE BLOCK CHANGE TRACKING";

Update the RMAN metadata.

CROSSCHECK ARCHIVELOG ALL;

Exit RMAN.

Start all RAC instances.

>srvctl START DATABASE -d <database_name>

Start all RAC Services.

>srvctl START SERVICE -d <database_name>

Ensure that all RAC instances are running.

>srvctl STATUS DATABASE -d <database_name>


	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.

Performing restores after node failure

If the multi-instance RAC database experiences a media failure or data corruption simultaneously with a failure of the node where the plug-in is installed, relocate the plug-in to an alternate node in the RAC environment to perform an RMAN-based restore and recovery. Relocating the plug-in is a two-step process:

Install the NetVault Backup Client software on an alternate node.

Install the NetVault Backup Client on an alternate node in the RAC environment.

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 database environment except that you install the plug-in 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 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.

Duplicating a database in a RAC environment

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.

Restoring a Duplicate Database backup to the same RAC Environment is almost identical to restoring a Duplicate Database backup in a single-instance environment. The differences are described in the following topics.

Seleziona il prodotto:

Per una maggiore efficacia, compilare l'Obiettivo della chat:

Soluzioni consigliate per il problema

NetVault Plug-in for Oracle 12.2 - User Guide

Prerequisites

Performing the disaster recovery

Performing restores after node failure

Duplicating a database in a RAC environment