Chatee ahora con Soporte
Chat con el soporte

NetVault Plug-in for Oracle 12.2 - 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

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 Backup software and Plug‑in for Oracle installed: The same version of NetVault Backup 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 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: 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 Backup Client and database, select the Whole Database node, and click Edit Plugin Options.
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 Backup 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.

Renaming or relocating files

With the RMAN backup method, the plug-in lets you rename the Control File and datafiles during restore. Renaming files can be useful if you do not want to overwrite the existing version and want to create a copy of the file. You can also relocate the files to a different directory while restoring it with the plug-in.

2
In the Navigation pane, click Create Restore Job, select Plug‑in for Oracle from the Plugin Type list.
4
On the Create Selection Set page, select the datafile or Control File to restore.
5
From the Actions list, select Rename.
6
In the Rename/Relocate dialog box, enter the applicable information.
Rename: Enter the new name.
Relocate: Enter the new path.
The plug-in uses the RMAN SET NEWNAME command to restore or rename — or both — RMAN backups. The SET NEWNAME command has precedence over the DB_CREATE_FILE_DEST parameter. If the full path is not specified for a restore or rename, the plug-in behaves as follows:
SPFILE: The file is restored to the “$ORACLE_HOME/dbs” directory with the new name.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación