Chatta subito con l'assistenza
Chat con il supporto

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

Recovering individual datafiles and tablespaces to the same server

This type of recovery is performed when the database is open, but some of the datafiles are damaged. This recovery is useful when you want to recover the damaged tablespace, while leaving the database open so that the rest of the database remains available. You can only perform Complete Recovery when restoring and recovering individual datafiles or tablespaces. PIT Recovery is not available for individual datafiles or tablespaces. Enabling PIT Recovery causes the restore job to fail. Following is an overview of the process to recover individual datafiles or tablespaces:

1
On the Create Selection Set page, select the damaged datafiles or tablespaces from the latest available backup of the tablespace, and click Edit Plugin Options.
2
Click the Restore Options tab, and select the Alter Tablespaces Offline Before Restore and the Alter Tablespaces Online After Restore options.
3
On the Perform Recovery tab, select the applicable options:
NOTE: If you select the Perform Database Point in Time Recovery option, the restore job fails.
To delete the restored archive logs that Oracle deems unnecessary, select the Delete Restored Archive Logs No Longer Needed option.
4
Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.

Recovering Whole Database to same server

This type of recovery is performed when the current Control File and SPFILE are intact but all the datafiles are damaged or lost. You can perform a Complete Recovery or recover the database to a specific point. Following is an overview of the process to recover the whole database, which must be performed when the database is in a MOUNT state:

1
On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next.
2
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.
3
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.
Perform Complete Recovery: Recovers the database to the current time, that is, to the last committed transaction available in the archived and online redo logs.
Perform Point-in-Time Recovery: Recovers the database to a specific point whether it be a specific time, log sequence number, or SCN.
5
On the Perform Recovery tab, select these additional options, if applicable:
To include read-only datafiles in the recovery process, select Check Read-Only Datafiles and Recover if Not Current. The read-only files are included only if they are needed to complete recovery. If they are not damaged, RMAN omits them.
6
On the Post Recovery tab, select Open Database after Recovery and Read Write and Reset Logs to open the database automatically in read-write mode and reset the online logs.
7
Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.

Performing disaster recovery with RMAN

Disaster recovery includes the restore and recovery of a database after the loss of the entire target database, all current Control Files, all online redo log files, and all parameter files. It is also assumed that the FRA has been lost. To perform a disaster recovery, the minimum required set of backups includes 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 new host, do not use these procedures. Instead, use the Duplicate Database backup type, which is designed for this purpose. For more information, see Duplicate Database backup.

The following methods are available for performing a disaster recovery:

When performing a disaster recovery of any kind, be aware of the following:

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
2
On the Create Restore Job — Choose Saveset page, select Plug‑in for Oracle from the Plugin Type list.
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.
5
Click Next.
6
On the Create Selection Set page, select any item.
7
Click Edit Plugin Options, and then click the Stepwise Disaster Recovery tab.
8
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:
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione