立即与支持人员聊天
与支持团队交流

NetVault Plug-in for Oracle 7.1 - User Guide

Introducing Dell™ 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-inin a failover cluster environment Using the plug-in with Oracle Data Guard Troubleshooting Glossary About Dell

Using RMAN types of recovery in a non-RAC environment

3
Use SET DBID to set the database identifier for the target database.
SET DBID <Source_DBID>;
Running the ALTER DATABASE OPEN RESETLOGS command from RMAN versus SQL*Plus resets the target database automatically so that you do not have to run a RESET DATABASE. By resetting the database, RMAN considers the new incarnation as the current incarnation of the database. If you run ALTER DATABASE OPEN RESETLOGS from SQL*Plus and do not follow it with a RESET DATABASE at the RMAN prompt, RMAN refuses to access the Recovery Catalog because it cannot distinguish between a RESETLOGS operation and an accidental restore of an old Control File.

Recovering individual datafiles/tablespaces to the same server

This type of recovery is performed when the database is open, but some of the datafiles are damaged. This 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 will only be able to perform Complete Recovery when restoring and recovering individual datafiles/tablespaces. PIT Recovery is not available for individual datafiles/tablespaces. Enabling PIT Recovery will cause the restore job to fail. Following is an overview of the process to recover individual datafiles/tablespaces:
1
On the Create Selection Set page, select the damaged datafiles/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 will fail.
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

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-in-time 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

If your goal is to create a new 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.
Objects selected the Create Selection Set page are ignored.
Only the options selected on the Stepwise Disaster Recovery tab are executed.
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, name of the NetVault Backup Server, name of the client from which the data was backed up, plug-in used to create the saveset, saveset creation date and time, saveset retirement setting, whether it is an Incremental Backup, whether it is an Archive, and saveset size.
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 will attempt 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 will attempt to recover all the datafiles in the Oracle database. This 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:
For variations on the following disaster recovery procedure, refer to Performing Disaster Recovery in the Oracle Database Backup and Recovery Advanced User’s Guide.
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 – Create the Oracle password file via the orapwd utility.
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 creates an identical Oracle Service name. For example, from an OS prompt execute:
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 or the Backup Contents tab.
Default location for SPFILE must exist – Make sure that the default location for the SPFILE exists. Failure to do so will result in an ORA-17502 Failed to create file error during the SPFILE restore.
Backups of all tablespaces made available – Make sure that you have the latest backups of all the tablespaces.
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.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级