Chat now with support
Chat with Support

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

Setting Generate RMAN Script options

Intended for the advanced DBA, the Generate RMAN Script feature lets you generate most of an RMAN script through the WebUI. Later, before using the script, you can add more options or parameters. With this option, you do not need to create the script from scratch, which minimizes the risk of syntax errors in the scripts and that restores are not performed correctly.

You can set the following options for the Generate RMAN Script feature:

•
Output RMAN Script to File: Select this option to use the feature and enable access to the remaining options, and then enter the name of the file to which the RMAN script is written.
•
RMAN Script Directory: Enter the name of the directory where the RMAN scripts are saved. The Generate Script Default Directory field defaults to the directory specified on the plug-in’s Configure dialog box. However, you can modify the field on a per-backup-job basis. The full path where the RMAN script is saved is built by concatenating the RMAN Script Directory with the filename provided in the Output RMAN Script to File field.
•
If Existing, Overwrite Destination File: Select this option to allow the destination file where the RMAN script is output to be overwritten if the file exists. If the file exists and this option is not selected, Generate RMAN Script fails and does not write output to the existing file. Select this option only if you are sure that you want to overwrite an existing file.
•
Generate RMAN Script and Submit Job: With this option selected, in addition to outputting the RMAN script to the specified file, the NetVault Backup Job is scheduled and submitted. Clearing this option ensures that the plug-in only generates the script, which lets you edit and run the script outside of NetVault Backup.
•
Do not Include Connect Strings: To exclude connection strings from the file because they might include Oracle passwords, select this option. Selecting this option ensures that Oracle passwords are not included in the RMAN script file.

Finalizing and submitting the job

Complete the steps outlined in Finalizing and submitting the job under Performing User Managed restores.

Using RMAN types of recovery in a non-RAC environment

The following topics describe the types of recovery that you can perform in a non-RAC environment:

•
Restoring the Control File from an Autobackup
•
Recovering individual datafiles and tablespaces to the same server
•
Recovering Whole Database to same server
•
Performing disaster recovery with RMAN

For information on the types of RMAN recoveries available in a RAC environment, see Restoring data in a RAC environment.

Restoring the Control File from an Autobackup

Restoring the Control File should only be performed in the following cases:

•
All current copies of the Control File have been lost due to a media failure or accidental user deletion, or have become corrupted and are not usable.
•
Oracle Customer Support has advised that a Control File restore is required.

As the Autobackup uses a default format, RMAN can restore it even if it does not have a repository available that lists the available backups. RMAN replicates the Control File to all CONTROL_FILES locations automatically.

1
Start RMAN, and connect to the target database:
>rman connect TARGET /
2
Start the target instance without mounting the database:
STARTUP FORCE NOMOUNT;
3
Use SET DBID to set the database identifier for the target database.
RMAN displays the DBID whenever you connect to the target. You can also obtain it by inspecting saved RMAN log files, querying the Catalog, or looking at the filenames of Control File Autobackup. For example, run:
SET DBID <Source_DBID>;
4
Restore the Control File Autobackup:
RUN {
ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';
RESTORE CONTROLFILE FROM AUTOBACKUP;
ALTER DATABASE MOUNT;
RESTORE DATABASE;
RECOVER DATABASE;
}
If the default format was modified for the Control File Autobackup, specify the same format during a restore:
RUN {
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE <device type> TO '<string>'
ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';
RESTORE CONTROLFILE FROM AUTOBACKUP;
ALTER DATABASE MOUNT;
RESTORE DATABASE;
RECOVER DATABASE;
}
5
Open the database, and reset the online logs:
ALTER DATABASE OPEN RESETLOGS;
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. RMAN refuses because it cannot distinguish between a RESETLOGS operation and an accidental restore of an old Control File.
 
* 
IMPORTANT: After restoring the Control File from an Autobackup, Quest recommends that you perform a Full or Incremental Level 0 backup with the database node selected on the NetVault Backup Selections page.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating