NetVault Plug-in for Oracle 12.2


	IMPORTANT: When restoring some or all of the required archived redo log files to an alternate location, specify the location before media recovery by using the LOGSOURCE parameter of the SET statement in SQL*Plus.

Performing RMAN restores

A standard RMAN restore with Plug‑in for Oracle includes the following steps:

•

Selecting data for a restore

•

Setting restore options

•

Finalizing and submitting the job

Selecting data for a restore

In the Navigation pane, click Create Restore Job.

On the Create Restore Job — Choose Saveset page, select Plug‑in for Oracle from the Plugin Type list.

To filter the items displayed in the saveset table further, use the Client, Date, and Job ID lists.

The table displays the saveset name (job title and saveset ID), creation date and time, and size. By default, the list is sorted alphabetically by saveset name.

The following table outlines the backup-type identifiers:


Backup type	Backup type identifier
RMAN Full Database	RMAN FULL DB
RMAN Incremental Level 0	RMAN INCRMTAL LVL 0
RMAN Cumulative Incremental	RMAN CUML INCRMTAL
RMAN Differential Incremental	RMAN DIFF INCRMTAL
RMAN Archive Log	RMAN ARCHIVE LOG
RMAN Control File and Parameter File	RMAN CTRL PARM
RMAN Flash Recovery Area	RMAN FRA
RMAN Duplicate Database	RMAN DUPL DB
All other RMAN Backups	RMAN Backup

In the saveset table, select the applicable item.

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 Next.

On the Create Selection Set page, with the Whole Database node and the other nodes based on the items selected for the backup displayed, select the applicable items:

•

Whole Database: Select this node if you want to Restore or Recover, or both, the entire database. With this option selected, you can perform the DBPITR based on SCN, LSN, or time to reconstruct the database up to the required point.

Selecting the All Tablespaces node or all the datafiles and tablespaces nodes is not equivalent to selecting this node.

•

Parameter File: Available only if the Control File Autobackup Enabled option is cleared on the Add, or Edit, Oracle Database dialog box.

When restoring a parameter file, select the backup that contains the specific version of the Parameter File that you want. For example, the Parameter File is backed up weekly on Sunday night at 11 p.m. Assuming today is Thursday and you need to restore the Parameter File to the state it was on Tuesday at 6 p.m., select the Parameter File from the last backup that occurred before Tuesday at 6 p.m., which would be Sunday night’s backup at 11 p.m.

•

SPFILE: For restore purposes, a node SPFILE is available in the restore selections if the backup contents include the backup of the SPFILE. If selected, it restores the SPFILE using RMAN commands — in particular the RESTORE SPFILE command.


	NOTE: An SPFILE cannot be restored to overwrite a live SPFILE, for example, if the database was started using the SPFILE. However, it can be restored to a different location. Use the Restore Rename feature of NetVault Backup and input the full path — full directory path and filename — of the location to which to restore the SPFILE.

Unlike the loss of the Control File, the loss of the SPFILE does not cause the Oracle Instance to stop running immediately. The Oracle Instance may continue operating while it is not shut down. You can restore a backed-up SPFILE to an alternate location. After the Oracle Instance is shut down, restart the Oracle Instance using the restored SPFILE, or copy the restored SPFILE to the default location and then restart the Oracle Instance.

•

Control File: You cannot open this node further. Also, if a Recovery Catalog is not in use, you cannot restore it from the WebUI. The restore fails if you try to include Control File in a restore job, unless Use Catalog is enabled on the Recovery Catalog tab.

When restoring the Control File from Manual Backup, select the backup that contains the specific version of the Control File that you want. For example, Manual Backups of the Control File are performed nightly at 11 p.m. Assuming today is Thursday and you need to restore the Control File to the state it was on Tuesday at 6 p.m., select the Control File from the last backup that occurred before Tuesday at 6 p.m., which would be Monday night’s backup at 11 p.m.

•

All Tablespaces: Select this node to perform an All Tablespace restore where all the tablespaces are restored consecutively with the RMAN RESTORE DATAFILE command. Performing an All Tablespace restore requires the database to be in a MOUNT state.

•

Individual Tablespaces/Datafiles: Open the All Tablespaces node to reveal the tablespaces available for restoration. You can select individual or multiple tablespaces, or open the tablespace node and select individual datafiles. Restoring individual tablespaces or datafiles requires the tablespace to be OFFLINE during the restore and recovery process.

•

External Configuration Files: You can expand this node to reveal the Oracle Network Configuration and Oracle Password files available for restore. Select this node to restore all the available External Configuration Files, or open it and select individual files. The plug-in uses the Plug-in for FileSystem functionality to restore the Oracle Network Configuration and Oracle Password files.