Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault Plug-in for Oracle 13.0 - User Guide

Introducing Quest® NetVault® 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

Performing backups after node failure

If the node where the plug-in is installed in the RAC environment experiences a node failure and the node is, or will be, unavailable at the time of the next scheduled backup, relocate the plug-in to an alternate node in the RAC environment.

Install the NetVault 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 Client on the original node. For example, if PROD_RAC was the NetVault Machine Name specified during the installation on the original node, PROD_RAC should be used as the NetVault Machine Name on the alternate node.
2
IMPORTANT: If the relocation of the plug-in is expected to be permanent or last longer than 45 days, visit https://support.quest.com/contact-us/licensing and request relocation of the RAC Database-Based Plug‑in for Oracle license files.

For more information on selecting data for backup, setting backup options, and finalizing and submitting the job, see Performing RMAN backups.

Restoring data in a RAC environment

Because RMAN is RAC-aware, it restores the selected data accordingly. With Plug‑in for Oracle installed on one of the nodes that hosts one of the instances for the RAC-enabled database, all RMAN-based restores are performed from this single installation of the plug-in. The restore process is similar to restoring single-instance, non-RAC environments, with the following exceptions:

During the Selecting data for a restore phase of performing RMAN restores, you might select a backup set from a node where the Oracle SID equals the Oracle SID of the instance on which the plug-in is running. But you might also select a backup set from an Oracle SID of a different RAC node for which backups were performed previously. For more information about performing restores after a node failure, see Performing restores after node failure.
During the Setting restore options phase, if authentication for the target database is needed, set the Target Database Authentication Details to the applicable values for the local Oracle instance on which the plug-in that is performing the restore 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.

The following topics outline additional types of RMAN recovery that are available in a RAC environment.

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.

2
Set the ORACLE_SID environment variable to the local instance.
3
Start SQL*Plus, and connect with administrator privileges to the local instance.
6
Disable the CLUSTER_DATABASE initialization parameter for the local instance.
8
Exit SQL*Plus.
> srvctl STOP DATABASE -d <database_name> -o abort
11
Start SQL*Plus, and connect with administrator privileges to the local instance.
12
In SQL*Plus, start the local instance with the MOUNT option.
13
On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Restore.
14
On the Create Selection Set page, select the Whole Database node, and click .
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.
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.
20
Start SQL*Plus, and connect with administrator privileges to the local instance.
21
Enable the CLUSTER_DATABASE initialization parameter for the local instance.
23
Exit SQL*Plus.

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.

2
Set the ORACLE_SID environment variable to the local instance.
3
Start SQL*Plus, and connect with administrator privileges to the local instance.
6
Disable the CLUSTER_DATABASE initialization parameter for the local instance.
8
Exit SQL*Plus.
>srvctl STOP DATABASE -d <database_name> -o abort
>rman TARGET / CATALOG rman/<password>@<connect_identifier for catalog>
12
SET DBID <DBID>;
17
Start SQL*Plus, and connect with administrator privileges to the local instance.
18
Enable the CLUSTER_DATABASE initialization parameter for the local instance.
20
Exit SQL*Plus.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation