Chat now with support
Chat with Support

NetVault Plug-in for Oracle 10.0.5 - 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-in in a failover cluster environment Using the plug-in with Oracle® Data Guard Troubleshooting Glossary

Performing restores after node failure

If the multi-instance RAC database experiences a media failure or data corruption simultaneously with a failure of the node where the plug-in is installed, relocate the plug-in to an alternate node in the RAC environment to perform an RMAN-based restore and recovery. Relocating the plug-in is a two-step process:
1
Install the NetVault Backup Client software on an alternate node.
Install the NetVault Backup Client on an alternate node in the RAC environment. During the installation process, be sure to use the same NetVault Machine Name that was used during the installation of the NetVault Backup Client on the original node. For example, if PROD_RAC was the NetVault Machine Name specified during the installation of the original node, PROD_RAC should be used as the NetVault Machine Name on the alternate node.
2
Install Plug‑in for Oracle.
After the NetVault Backup Client has been installed on the selected node of the RAC environment, install the plug-in. The process is identical to installing the plug-in for a single-instance database environment except that you install the plug-in on the NetVault Backup Client that corresponds with the generic or virtual name provided as the NetVault Machine Name during the NetVault Backup Client installation.
 
* 
IMPORTANT: If the relocation of the plug-in is expected to be permanent or last longer than 45 days, visit https://support.quest.com/licensing-assistance to request relocation of the RAC Database-Based Plug‑in for Oracle license keys.
With Plug‑in for Oracle installed on the alternate node, the restore process is similar to performing restores in a single-instance, non-RAC environment except for the following differences:
•
During the Selecting data for a restore phase of performing RMAN restores, select the backup set from the node on the Create Selection Set page where the Oracle SID equals the Oracle® SID of the instance where the plug-in was originally installed before the relocation.
•
During the Setting restore options phase, set the Target Database Authentication Details to the appropriate values for the local instance on the alternate node where the plug-in now resides. For more information, see Setting Destination Details.
For more information on preparing the database for recovery, selecting data items for a restore, setting restore options, finalizing and submitting the job, and opening the database for use, see Performing RMAN restores.

Duplicating a database in a RAC environment

A Duplicate Database backup lets you create a duplicate or clone of a source database for special purposes that must not affect the overall backup and restore procedures for the source database. In a RAC environment, Oracle® does not support duplicating a multi-instance database to a different multi-instance database. However, Oracle does support duplicating a multi-instance database to a single-instance database followed by converting the single-instance database to a multi-instance database. For more information, see the Oracle Real Application Clusters Installation Guide.
Restoring a Duplicate Database backup to the same RAC Environment is almost identical to restoring a Duplicate Database backup in a single-instance environment. The differences are described in the following sections.
Prerequisites
PFILE updated with auxiliary values: In addition to the updates to the PFILE as specified in the Non-RAC duplication procedures, the following additional updates must be made when the source database is a multi-instance database:
1
Comment out the RAC-related parameters by inserting a “#” (number sign) at the start of the entry.
Sample RAC-related parameters include:
•
.cluster_database_instances = N
•
.cluster_database=TRUE
•
<database/instance_name>.cluster_database=TRUE
•
<instance_name>.instance_number=N
•
<instance_name>.thread = N
•
<instance_name>.undo_tablespace = '<tablespace_name>'
2
Add the following parameters:
<auxiliary_instance_name>.undo_tablespace='<undo_tablespace>'
<auxiliary_instance_name>.thread = 1

Post-restore procedure

After completion of the Restore Duplicate Database Procedure as defined in the Duplicating a database in a non-RAC environment, you can convert the resulting single-instance database to a multi-instance database. To do so, use one of the procedures detailed in Converting to Oracle® Real application Clusters from Single-Instance Oracle Databases in the Oracle Real Application Clusters Installation Guide.

Using the Plug-in in a failover cluster environment

•
Oracle Server Fail Safe Failover Clustering: an overview
•
Installing the plug-in
•
Licensing the plug-in
•
Configuring the plug-in and adding a database
•
Backing up data
•
Restoring data
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating