Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for Oracle 11.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 Troubleshooting

RAC configuration requirements

Plug‑in for Oracle’s support for multi-instance RAC databases is limited to environments that meet the following criteria:

The version of Oracle® and the platform are listed as a supported RAC environment in Quest NetVault Backup Compatibility Guide.

Figure 6 and Figure 7 provide an overview of supported single and multiple RAC database deployments.

Installation prerequisites

The following prerequisites must be met before you can install Plug‑in for Oracle in a RAC environment:

Oracle® RAC environment in place: You must have a properly configured Oracle RAC environment that matches the configuration as specified in RAC configuration requirements.
Separate NetVault Backup Server machine: The machine that is to serve as the NetVault Backup Server must be properly configured. This machine must exist outside the Oracle RAC environment, but have network connectivity to the nodes and hosts within the RAC environment.
Separate Recovery Catalog Server: Quest recommends that you store the RMAN repository in a Recovery Catalog database on a server outside the Oracle RAC environment. For more information, see Creating the RMAN repository.
Additional prerequisites: In addition to the preceding RAC-specific requirements, meet the requirements that are specified in Prerequisites.
Oracle 11g Release 2 and later: If you are using Oracle 11g Release 2 or later, ensure that the snapshot Control File is shared by all nodes in the RAC database. The snapshot Control File must be saved in a shared location, such as in one ASM instance or on a shared drive. The location of the snapshot Control File is managed by the snapshot Control File name RMAN parameter. In Oracle 11g Release 2, by default, this parameter refers to a persistent file in the local file system on each of the RAC nodes. If this configuration applies to your environment, ensure that you change the parameter to point to a shared location. Otherwise, RMAN backups that include the Control File might fail with an “ORA-00245: control file backup operation failed” message.

Enabling Control File Autobackups in a RAC environment

Control File Autobackups are required in a RAC environment. For more information, see Reviewing the Control File backup types. For more information on single-instance RAC databases, see Enabling Control File Autobackups.

You can turn the Autobackup feature on for multi-instance RAC databases by running the following commands from the RMAN command-line utility on the node where the plug-in will be installed:

> rman TARGET / CATALOG rman/<password>@<connect_identifier for catalog>
'SYS/<password>@<connect_identifier for local instance>';

Installing or upgrading the plug-in

Installing Plug‑in for Oracle in a multi-instance database environment is almost identical to installing it in a single-instance database environment. The plug-in is installed on one of the nodes that hosts one of the instances for the RAC-enabled database. All RMAN-based backups and restores are performed from this single installation of the plug-in. Installing the plug-in is a two-step process:

1
Install the NetVault Backup Client software.
During installation of the NetVault Backup Client software on the selected node of the RAC environment, a name that represents the entire RAC environment should be specified as the NetVault Machine Name versus the machine name of the selected node. For example, if the machine name for the node where the NetVault Backup Client software is being installed is called RAC_NODE_1, RAC_NODE_1 should not be specified as the NetVault Machine Name; it should be a generic or virtual name that represents the entire RAC environment such as PROD_RAC.
2
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione