NetVault Plug-in for Oracle 13.0

When you select a saveset, the following details are displayed in the Saveset Information area: Job ID, job title, server name, client name, plug-in name, saveset date and time, retirement setting, Incremental Backup or not, Archive or not, and saveset size.

Click Restore.

On the Create Selection Set page, select any item.

As explained earlier, selections on this page are ignored for this process.

Click

, and then click the Stepwise Disaster Recovery tab.

Select the Perform the following Step-by-Step Disaster Recovery option, and then select the applicable suboptions:

•

Set Dbid: If you want to specify the DBID, select this option. The plug-in automatically enters the DBID of the Oracle database for which the backup was taken in this field. The DBID is needed when a parameter file or SPFILE is not available to start the Oracle database in a NOMOUNT state.

•

Restore Spfile from Autobackup; Look Back Max Days: If the Oracle Control File Autobackup option was enabled in your scheduled backups and you want to restore the SPFILE from an Autobackup, select this option. If Oracle Control File Autobackup was not enabled, you cannot restore the SPFILE from an Autobackup; for more information, see Enabling Control File Autobackups. By default, this option looks for Autobackups in the last seven days; update it as applicable. This option issues the following RMAN commands:

STARTUP NOMOUNT;

restore spfile from autobackup maxdays <NumberOfDays>;

•

Restore Controlfile from Autobackup; Look Back Max Days: If the Oracle Control File Autobackup option was enabled in your scheduled backups and you want to restore the Control File from an Autobackup, select this option. If Oracle Control File Autobackup was not enabled, you cannot restore the Control File from an Autobackup; for more information, see Enabling Control File Autobackups. By default, this option looks for Autobackups in the last seven days; update it as applicable. This option issues the following RMAN commands:

STARTUP FORCE NOMOUNT;

restore controlfile from autobackup maxdays <NumberOfDays>;

•

Restore Database: If you want to restore all datafiles included in the Oracle database, select this option. A RESTORE DATABASE command attempts to restore all the datafiles in the Oracle database. This option issues the following RMAN command:

RESTORE DATABASE;

•

Recover Database: If you want to recover all datafiles included in the Oracle database, select this option. A RECOVER DATABASE command attempts to recover all the datafiles in the Oracle database. This recovery might include automatically restoring and applying archived transaction logs. This option issues the following RMAN command:

RECOVER DATABASE;

•

Alter Database Open Resetlogs: If you want to open the database with the RESETLOGS option, select this option. This option issues the following SQL*Plus command:

ALTER DATABASE OPEN RESETLOGS;


	NOTE: With the database restored, you have the option of opening an RMAN CLI prompt and issuing the recovery commands from the prompt. This option eliminates the need to select the Recover Database and Alter Database Open Resetlogs options and lets you issue advanced recovery options.

Complete the steps in Finalizing and submitting the job.

Disaster recovery to same server

The following procedure details the steps to perform disaster recovery to the same server where the source database resided. This procedure would be used in the scenario in which a complete media failure occurred and either the damaged host was rebuilt using the same configuration or a new server was configured imitating the original host’s configuration, including host name.


	NOTE: You can also use the following procedure to restore the Oracle Server to a different host, one that is not the original production server, while the production server is still active. However, as stated previously, if your goal is create a copy of the target production database for ongoing use on a new host, do not use this procedure. Instead, use the Duplicate Database backup type. For more information, see Duplicate Database backup.

The same procedure should be used whether a Recovery Catalog was being used as part of the backup strategy for the RMAN Repository. RMAN always stores information concerning the backups in records in the Control File. The version of this information in the Control File is the authoritative record of RMAN’s backups of your database. RMAN can conduct all necessary backup and recovery operations using just the repository information in the Control File.

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

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

•

Oracle database software installed: Install the same version of the Oracle database software on the system as existed on the damaged server. The ORACLE_HOME should be identical on both the source and destination Oracle server. You do not have to create the database.

•

Oracle password file created: Use the orapwd utility to create the Oracle password file.

•

On Linux:

orapwd file=<Oracle_Home>/dbs/orapw<SID> password=<password>

•

On Windows:

orapwd file=<Oracle_Home>\database\orapw<SID> password=<password>

•

Oracle service on Windows created and started: Create the Oracle Service on Windows with Oracle’s oradim utility. The Oracle SID should be identical to the original or source database. This option creates an identical Oracle Service name. For example, from an OS prompt run:

oradim -new -sid <sid_name>

After the Windows service is created, start the service with the following command from an OS prompt:

net start oracleservice<sid_name>

•

NetVault software and Plug‑in for Oracle installed: The same version of NetVault software and the plug-in must be installed and configured as it originally existed on the damaged server. Ensure that the plug-in’s default attributes are defined as specified in Configuring default settings.

•

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 for Oracle installation, look for it in the NetVault 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: Verify that the default location for the SPFILE exists. Failure to do so results in an ORA-17502 Failed to create file error during the SPFILE restore.

•

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

To perform the recovery, complete the following steps.

Restore the Oracle Net Services Configuration Files.

If the External Configuration Files were included in a previous RMAN backup or the Plug-in for FileSystem was used to back up the Oracle Net Services configuration files, such as “listener.ora,” “sqlnet.ora,” and “tnsnames.ora,” restore the files to the destination Oracle Database Server. Otherwise, configure the Oracle Net Services on the destination Oracle server.

Start the Oracle listener.

For example, from an OS command prompt run:

lsnrctl start

Start RMAN with no catalog, and connect to the target database:

RMAN TARGET / NOCATALOG

Set the DBID to the damaged database DBID.

SET DBID <Source_DBID>;

Start the target instance without mounting the database.


	IMPORTANT: A series of Oracle errors might appear if a PFILE is not available when you run the following command. This process is acceptable, and you can ignore the errors. Oracle uses a default PFILE to ensure that the restore process for the SPFILE continues — “starting Oracle instance without parameter file for retrieval of spfile.”

STARTUP NOMOUNT;

Restore the SPFILE from Autobackup.

RUN {

ALLOCATE CHANNEL C1 TYPE 'SBT_TAPE';

RESTORE SPFILE FROM AUTOBACKUP;

}

Restart the database with the restored SPFILE.

STARTUP FORCE NOMOUNT;

Restore the Control File from Autobackup.

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

RUN {

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

RESTORE CONTROLFILE FROM AUTOBACKUP;

}


	IMPORTANT: If you do not have an Autobackup of the Control File, complete the steps in Retrieving a Control File manually before continuing.

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 Client and database, select the Whole Database node, and click

Click the Restore Options tab, and select the applicable options:

•

To mount the database before the performing the restore, select Mount Database Before Restore.

•

To include read-only datafiles in the restore, select Check Read-Only Datafiles and Restore if Necessary.

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 Perform Recovery tab, select Check Read-Only Datafiles and Recover if Not Current to include read-only datafiles in the recovery process.

The read-only files are included only if they are needed to complete recovery. If they are not damaged, RMAN omits them.

On the Recovery Catalog tab, clear the Use Catalog option to ensure that the Recovery Catalog is not used for this restore.

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

RMAN automatically chooses the best available Full, Incremental, or Archive Log backups and restore and recover the database.

In RMAN, update the RMAN metadata.

CROSSCHECK ARCHIVELOG ALL;

Exit RMAN.


	IMPORTANT: After completing a disaster recovery, Quest recommends that you perform a Full or Incremental Level 0 backup with the database selected on the Create Selection Set page.