Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for Oracle 13.0 - User Guide

Introducing Quest® NetVault® 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

Using the Stepwise Disaster Recovery process

This process runs a restore of the Control File from an Autobackup and restores the database datafiles using the same restore task. If you use this process, be aware of the following:

Objects selected on the Create Selection Set page are ignored.
Only the options selected on the Stepwise Disaster Recovery tab are run.
1
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.
4
Click Restore.
5
On the Create Selection Set page, select any item.
6
Click , and then click the Stepwise Disaster Recovery tab.
7
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:
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:
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:
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:
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:

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.

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.
orapwd file=<Oracle_Home>/dbs/orapw<SID> password=<password>
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:
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.

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.
SET DBID <Source_DBID>;
6
Restore the SPFILE from Autobackup.
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 Client and database, select the Whole Database node, and click .
11
Click the Restore Options tab, and select the applicable options:
To include read-only datafiles in the restore, select Check Read-Only Datafiles and Restore if Necessary.
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 Perform Recovery tab, select Check Read-Only Datafiles and Recover if Not Current to include read-only datafiles in the recovery process.
14
On the Recovery Catalog tab, clear the Use Catalog option to ensure that the Recovery Catalog is not used for this restore.
15
Complete the Schedule and Advanced Options tabs, and submit the job.

Retrieving a Control File manually

When Control File Autobackups are not available, the RMAN Catalog is not used, and only Control File backups were performed by selecting the Control File node on the NetVault Selections page, you might be able to use the following procedure to extract the Control File from a backup piece.

1
On the Create Restore Job — Choose Saveset page, find the latest available backup that is marked with “Controlfile Included.”
('<destination PathAndNameOfControlFile>');
('<backupSegment NameIdentifiedEarlier>',done=>done);
3
Use the REPLICATE CONTROLFILE command to copy the restored Control File.
SET DBID <Source_DBID>;
'<sourcePathAndNameOfControlFile>';

Using advanced procedures with RMAN restores

This topic contains subtopics that describe other restore operations that can be performed with Plug‑in for Oracle.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione