• Become a portal pro
• Download
• Print
• My Downloads ()

• Support
• Technical Documentation
• NetVault Plug-in for Oracle 12.2
• NetVault Plug-in for Oracle 12.2 - User Guide

NetVault Plug-in for Oracle 12.2 - User Guide

Table of Contents  

Introducing Quest® NetVault® Backup Plug-in  for Oracle

Quest NetVault Backup Plug-in for Oracle: at a glance Key benefits Feature summary Target audience Recommended additional reading

Defining a backup strategy

Defining a strategy: overview Reviewing the available backup methods

User Managed backup method Recovery Manager (RMAN) backup method

Reviewing the supported Oracle file types Defining an RMAN backup strategy

Choosing the location for the RMAN repository Reviewing the RMAN Tablespace and Datafile backup types Reviewing the Control File backup types Reviewing the other backup types

Flash Recovery Area (FRA) backups

Developing a Recovery Catalog backup strategy Examples of backup sequences Defining a Backup Destination strategy

Oracle Flashback technology NetVault Backup Policy Management

Installing and removing the plug-in

Prerequisites

NetVault Backup Server and Client software Database in ARCHIVELOG mode

Prerequisites for RMAN backups

Adding the Oracle user to the local administrator group on Windows Determining the Oracle SID and Home directory in a non-RAC environment

Windows Linux and UNIX

Creating the RMAN repository

Configuring the Recovery Catalog database Creating the Recovery Catalog owner Creating the Recovery Catalog

Registering the target database Enabling Control File Autobackups Enabling Flashback Database

Determining whether Flashback Database is enabled Setting a retention target

Enabling Block Change Tracking

Recommended configuration for a single-instance non-RAC environment Installing or upgrading the plug-in Removing the plug-in

Configuring the plug-in

Configuring a default Target Set for RMAN backups Configuring default settings Adding a database

Editing database information Setting the database password Removing a saved password Removing a database Viewing database details Using RMAN Post-Backup Scripts

Creating an RMAN Post-Backup Script Updating a Post-Backup Script Removing a Post-Backup Script

Language support

Backing up data

Performing User Managed backups

Selecting data for a backup Selecting backup options Finalizing and submitting the job

Performing RMAN backups

Selecting data for a backup Setting backup options Finalizing and submitting the job

Using Plug-in for FileSystem to back up Oracle ACFS

Using the Oracle Flashback Database

Flashback Database: an overview

Flashback Logs

Viewing Flashback Database status Flashback Database options Flashback Database restrictions Restoring data with the plug-in and Flashback Database

Restoring data

Restoring and recovering data: an overview

Understanding User Managed recovery

Determining which datafiles require recovery Recovering datafiles and archive logs Restoring Control Files

Understanding RMAN recovery

How RMAN backups are selected for use in recovery operations Choosing between Incremental Backups and Redo Logs Choosing the restore source Datafile media recovery Block Media Recovery

Performing User Managed restores

Preparing the database for recovery Selecting data for a restore Finalizing and submitting the job Recovering the database Opening the database for use

Using advanced User Managed restore procedures

Renaming or relocating Control File, Datafile, or individual Archived Log files Renaming or relocating the Archive Log Directory

Performing RMAN restores

Selecting data for a restore Setting restore options

Viewing the contents of backup pieces Setting the Pre-Restore and general Restore Options Setting recovery options Setting Block Media Recovery options Setting Post Recovery options Setting Destination Details Setting the Recovery Catalog details Setting the Clone Database options Setting Generate RMAN Script options

Finalizing and submitting the job

Using RMAN types of recovery 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

Using the Stepwise Disaster Recovery process Disaster recovery to same server Retrieving a Control File manually

Using advanced procedures with RMAN restores

Renaming or relocating files Duplicating a database in a non-RAC environment

Restoring a Duplicate Database to the same server Restoring a Duplicate Database to an alternate server with the same directory structure Restoring a Duplicate Database to an alternate server with an alternate directory structure

Performing table-level recovery

Uses of table-level recovery Table-level requirements and limitations Configuring channels for table-level recovery Performing table-level recovery from the RMAN CLI Performing table-level recovery from the NetVault Backup WebUI

Maintaining the Recovery Catalog

Resynchronizing the Recovery Catalog

Using CROSSCHECK to update the RMAN repository

Using the RMAN CLI

CLI-based RMAN backups and restores: an overview Prerequisites for CLI-based backups and restores

Verifying that the proper RMAN executable is in use (Linux only) Ensuring an "SBT_TAPE" channel is established Running the NetVault Backup 'nvpluginaccess' utility

Performing CLI-based backups

Example of a basic CLI backup More parameters: the "format" clause More parameters: the "send" and "PARMS" clauses Querying the NetVault Backup media name

Performing CLI-based restores

Using the Plug-in with Oracle RAC

Oracle RACs: an overview Recommended additional reading Defining a deployment strategy

RMAN backup process for RAC environment RMAN restore process for RAC environment

Licensing Installing the plug-in in a RAC environment

RAC configuration requirements Installation prerequisites

Enabling Control File Autobackups in a RAC environment

Installing or upgrading the plug-in

Configuring the plug-in

Configuring default attributes Determining the local Oracle SID and Home directory in a RAC environment Adding a database to the plug-in

Backing up data

Performing backups after node failure

Restoring data in a RAC environment

Recovering a Whole Database to the same RAC environment Restoring SPFILE in a RAC environment Restoring Control Files in a RAC environment Performing disaster recovery in a RAC environment

Prerequisites Performing the disaster recovery

Performing restores after node failure Duplicating a database in a RAC environment

Prerequisites Post-restore procedure

Using the Plug-in in a failover cluster environment

Oracle Server Fail Safe Failover Clustering: an overview Installing the plug-in

Installation prerequisites Installing or upgrading the software

Creating a Virtual Client

Licensing the plug-in Configuring the plug-in and adding a database Backing up data Restoring data

Using the plug-in with Oracle Data Guard

Oracle Data Guard: an overview Defining a deployment strategy

Back up from Primary only Back up from both Primary and Standby Back up from Standby only

Deployment

Single-instance to single-instance Data Guard deployment Multi-instance RAC to single-instance Data Guard deployment Multi-instance RAC to multi-instance RAC Data Guard deployment

Installing the plug-in in a Data Guard environment

Installation prerequisites

Optional RMAN configuration settings

Installing or upgrading the plug-in

Backing up data

Creating a User Defined Backup Tag Performing manual backups of Control File and SPFILE

Restoring data

Configuring a restore to an alternate server in a Data Guard environment Restoring data to an alternate server in a Data Guard environment Recovering Whole Database to Primary Database Server

Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs)

Oracle PDBs: an overview Enabling connection to a PDB Querying CDB, PDB, and non-CDB databases Restrictions for backing up and restoring a PDB Backing up data Restoring data

Troubleshooting

Unable to add a database Backup fails Backup job hangs Restore fails Oracle RMAN output is not displayed correctly in binary logs

• Viewing Topics 165 - 168 of 218

×

Recovering a Whole Database to the same RAC environment

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 in a RAC environment.

1	From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed.

2	Set the ORACLE_SID environment variable to the local instance.

export ORACLE_SID = <local_SID>

3	Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

4	Shut down the local instance.

SHUTDOWN ABORT;

5	Start the local instance with the NOMOUNT option.

STARTUP FORCE NOMOUNT;

6	Disable the CLUSTER_DATABASE initialization parameter for the local instance.

ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=SPFILE SID='<local_SID>';

7	Shut down the local instance.

SHUTDOWN ABORT;

8	Exit SQL*Plus.

9	Shut down all RAC instances.

> srvctl STOP DATABASE -d <database_name> -o abort

10	Ensure that all RAC instances are shut down.

>srvctl STATUS DATABASE -d <database_name>

11	Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

12	In SQL*Plus, start the local instance with the MOUNT option.

STARTUP MOUNT;

13	On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next.

14	On the Create Selection Set page, select the Whole Database node, and click Edit Plugin Options.

15	Click the Restore Options tab, and select the applicable options:

•

To include read-only datafiles in the restore and recovery process, select Check Read-Only Datafiles and Restore if Necessary and 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.

•	To delete the restored archive logs that Oracle deems unnecessary, select the Delete Archive Logs No Longer Needed option.

16	To perform recovery on the database, that is, to reconstruct the database up to the current or specified point, select one of the following options on the Perform Recovery tab:

•	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 Database Point-in-Time Recovery: Recovers the database to a specific point whether it be a specific time, log sequence number, or SCN.

17	On the Recovery Catalog tab, select the Use Catalog option, and specify the Recovery Catalog connection details.

18	Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.

RMAN automatically chooses the best available full, incremental, or Archived Log backups, and restores and recovers the database.

19	From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed.

20	Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

21	Enable the CLUSTER_DATABASE initialization parameter for the local instance.

ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=SPFILE SID='<local_SID>';

22	Shut down the local instance.

SHUTDOWN ABORT;

23	Exit SQL*Plus.

24	Start all RAC instances.

>srvctl START DATABASE -d <database_name>

25	Start all RAC Services.

>srvctl START SERVICE -d <database_name>

26	Ensure that all RAC instances are running.

>srvctl STATUS DATABASE -d <database_name>

 

IMPORTANT: After completing a restore of the Whole Database, Quest recommends that you perform a Full or Incremental Level 0 backup with the entire database selected on the NetVault Backup Selections page.

Restoring SPFILE in a RAC environment

Because Control File Autobackups are a prerequisite in a multi-instance RAC environment, the SPFILE is backed up with the Control File whenever an Autobackup is performed. The SPFILE is restored from the Autobackup to the default location; for more information, see the following steps. If the instance is already started with the server parameter file, you cannot overwrite the existing server parameter file. For more information on restoring an SPFILE to a non-default location, see the Oracle Database Backup and Recovery Basics guide.

1	From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed.

2	Set the ORACLE_SID environment variable to the local instance.

export ORACLE_SID = <local_SID>

3	Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

4	Shut down the local instance.

SHUTDOWN ABORT;

5	Start the local instance with the NOMOUNT option.

STARTUP FORCE NOMOUNT;

6	Disable the CLUSTER_DATABASE initialization parameter for the local instance.

ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=SPFILE SID='<local_SID>';

7	Shut down the local instance.

SHUTDOWN ABORT;

8	Exit SQL*Plus.

9	Shut down all RAC instances.

>srvctl STOP DATABASE -d <database_name> -o abort

10	Ensure that all RAC instances are shut down.

>srvctl STATUS DATABASE -d <database_name>

11	Start RMAN, and connect to the target database and Recovery Catalog.

>rman TARGET / CATALOG rman/<password>@<connect_identifier for catalog>

12	Start the local instance with the FORCE NOMOUNT option.

STARTUP FORCE NOMOUNT;

13	Set the database identifier for the target database with SET DBID.

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. The DBID is also available on the Details dialog box or the Backup Contents tab.

SET DBID <DBID>;

14	Restore the SPFILE Autobackup.

If you are restoring the SPFILE to the default location, run:

RUN {

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

RESTORE SPFILE FROM AUTOBACKUP;

}

15	Start the instance with the FORCE option.

STARTUP FORCE;

16	Exit RMAN.

17	Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

18	Enable the CLUSTER_DATABASE initialization parameter for the local instance.

ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=SPFILE SID='<local_SID>';

19	Shut down the local instance.

SHUTDOWN ABORT;

20	Exit SQL*Plus.

21	Start all RAC instances.

>srvctl START DATABASE -d <database_name>

22	Start all RAC Services.

>srvctl START SERVICE -d <database_name>

23	Ensure that all RAC instances are running.

>srvctl STATUS DATABASE -d <database_name>

Restoring Control Files in a RAC environment

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.

Because Control File Autobackups are a prerequisite in a multi-instance RAC environment, perform the following steps to restore the Control Files from the Autobackup.

1	From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed.

2	Set the ORACLE_SID environment variable to the local instance.

export ORACLE_SID = <local_SID>

3	Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

4	Shut down the local instance.

SHUTDOWN ABORT;

5	Start the local instance with the NOMOUNT option.

STARTUP FORCE NOMOUNT;

6	Disable the CLUSTER_DATABASE initialization parameter for the local instance.

ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=SPFILE SID='<local_SID>';

7	Shut down the local instance.

SHUTDOWN ABORT;

8	Exit SQL*Plus.

9	Shut down all RAC instances.

>srvctl STOP DATABASE -d <database_name> -o abort

10	Ensure that all RAC instances are shut down.

>srvctl STATUS DATABASE -d <database_name>

11	Start RMAN, and connect to the target database.

>rman TARGET /

12	Start the local instance with the FORCE NOMOUNT option.

STARTUP FORCE NOMOUNT;

13	Set the database identifier for the target database with SET DBID.

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. The DBID is also available on the Details dialog box or the Backup Contents tab.

SET DBID <DBID>;

14	Restore the Control File Autobackup.

If you are restoring the Control File from the last Autobackup, run:

RUN {

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

RESTORE CONTROLFILE FROM AUTOBACKUP;

ALTER DATABASE MOUNT;

RESTORE DATABASE;

RECOVER DATABASE;

}

15	Open the database with the RESETLOGS option.

ALTER DATABASE OPEN RESETLOGS;

16	Exit RMAN.

17	Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

18	Enable the CLUSTER_DATABASE initialization parameter for the local instance.

ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=SPFILE SID='<local_SID>';

19	Shut down the local instance.

SHUTDOWN ABORT;

20	Exit SQL*Plus.

21	Start all RAC instances.

>srvctl START DATABASE -d <database_name>

22	Start all RAC Services.

>srvctl START SERVICE -d <database_name>

23	Ensure that all RAC instances are running.

>srvctl STATUS DATABASE -d <database_name>

 

IMPORTANT: After restoring a Control File from an Autobackup, Quest recommends that you perform a Full or Incremental Level 0 backup with the entire database selected on the NetVault Backup Selections page.

Performing disaster recovery in a RAC environment

Disaster recovery includes the restore and recovery of a multi-instance RAC database after a complete media failure of all the shared storage including the current Control Files, all online redo log files, all parameter files, and the Recovery Catalog. To perform a disaster recovery, you need the minimum required set of backups; the minimum includes the 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 standby RAC environment or independent RAC environment, do not use these procedures. Instead, use the Duplicate Database backup type, which is designed for this purpose. For more information, see Duplicating a database in a RAC environment.

 

IMPORTANT: When performing a test recovery, ensure that you do not connect to the Recovery Catalog during datafile restoration. Otherwise, RMAN records information about the restored datafiles to the Recovery Catalog. This recording interferes with future attempts to restore and recover the primary database. If you must use a Recovery Catalog because the Control File is not large enough to contain the RMAN repository data on all the backups that you need to restore, export the catalog and import it into a different schema or database, and use the copied Recovery Catalog for the test restore. Otherwise, the catalog considers the restored database as the current target database.

The following procedure details the steps to perform disaster recovery to the same RAC environment where the source database resided. This procedure would be used in the scenario in which a complete media failure of the shared storage occurred and the damaged shared storage was rebuilt using the same configuration or new shared storage was configured imitating the original shared storage’s configuration.

For variations on the following disaster recovery procedure, see Performing Disaster Recovery in the Oracle Database Backup and Recovery Advanced User’s Guide.

•	Prerequisites

•	Performing the disaster recovery

•  Previous
• Viewing Topics 165 - 168 of 218
• Next 

Search this document Search all documents

×

 Welcome to Quest Support

You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center