Chat now with support
Chat with Support

NetVault Plug-in for Oracle 12.3 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for Oracle Defining a backup strategy Installing and removing the plug-in Configuring the plug-in Backing up data Using the Oracle Flashback Database Restoring data
Restoring and recovering data: an overview Performing User Managed restores Using advanced User Managed restore procedures Performing RMAN restores Using RMAN types of recovery in a non-RAC environment Using advanced procedures with RMAN restores
Maintaining the Recovery Catalog Using the RMAN CLI Using the plug-in with Oracle RAC Using the plug-in in a failover cluster environment Using the plug-in with Oracle Data Guard Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs) Troubleshooting

Restoring Control Files in a RAC environment

Restoring the Control File should only be performed in the following cases:

Because Control File Autobackups are a prerequisite in a multi-instance RAC environment, perform the following steps to restore the Control Files from the Autobackup.

2
Set the ORACLE_SID environment variable to the local instance.
3
Start SQL*Plus, and connect with administrator privileges to the local instance.
6
Disable the CLUSTER_DATABASE initialization parameter for the local instance.
8
Exit SQL*Plus.
>srvctl STOP DATABASE -d <database_name> -o abort
12
SET DBID <DBID>;
15
17
Start SQL*Plus, and connect with administrator privileges to the local instance.
18
Enable the CLUSTER_DATABASE initialization parameter for the local instance.
20
Exit SQL*Plus.

Performing disaster recovery in a RAC environment

Disaster recovery includes the restore and recovery of a multi-instance RAC database after a complete media failure of all the shared storage including the current Control Files, all online redo log files, all parameter files, and the Recovery Catalog. To perform a disaster recovery, you need the minimum required set of backups; the minimum includes the backups of all the datafiles, some archived redo logs generated after the time of the backup, and at least one Autobackup of the Control File.

If your goal is to create a copy of your target database for ongoing use on a standby RAC environment or independent RAC environment, do not use these procedures. Instead, use the Duplicate Database backup type, which is designed for this purpose. For more information, see Duplicating a database in a RAC environment.

The following procedure details the steps to perform disaster recovery to the same RAC environment where the source database resided. This procedure would be used in the scenario in which a complete media failure of the shared storage occurred and the damaged shared storage was rebuilt using the same configuration or new shared storage was configured imitating the original shared storage’s configuration.

For variations on the following disaster recovery procedure, see Performing Disaster Recovery in the Oracle Database Backup and Recovery Advanced User’s Guide.

Prerequisites

To perform a disaster recovery without a Recovery Catalog, the following requirements must be met:

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

SET DBID <DBID>;
3
5
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
On the Recovery Catalog tab, clear the Use Catalog option.
14
Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.
Related Documents