サポートと今すぐチャット
サポートとのチャット

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

Restoring data in a RAC environment

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, you must 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.
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.
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 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.
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

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.

Restoring Control Files in a RAC environment

Oracle® Customer Support has advised that a Control File restore is required.
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
12
SET DBID <DBID>;
15
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.

Performing disaster recovery in a RAC environment

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.
For variations on the following disaster recovery procedure, see Performing Disaster Recovery in the Oracle® Database Backup and Recovery Advanced User’s Guide.
Oracle® RAC environment in place: You must have a properly configured Oracle RAC environment that matches the configuration as specified Performing User Managed backups. In addition, the same version of the Oracle database software must be installed in the RAC environment as it existed on the damaged RAC environment. The ORACLE_HOME should be identical on both the original and new node. You do not have to create the database, but you do need to configure Oracle Net Services and ASM for shared storage.
NetVault Backup software and the Plug‑in for Oracle installed: The same version of NetVault Backup software and the plug-in must be installed on one of the nodes in the RAC using the same NetVault Machine Name as previously defined for the RAC environment. Ensure that the plug-in default attributes are defined as specified in Configuring default attributes.
DBID of the source database identified: Identify the DBID of the damaged database. If the DBID was not recorded as part of the initial plug-in installation, you can obtain the DBID by examining the NetVault Backup binary logs for RMAN-based backups of the source database. The DBID is also available on the Details dialog box or the Backup Contents tab.
Default Location for SPFILE must exist: The default location in the ASM shared storage must exist before performing the following steps. Failure to ensure that the default location exists results in an ORA-17502 Failed to create file error during the SPFILE restore. Additionally, the SPFILE location should be detailed in the PFILE with the SPFILE parameter.
Backups of all tablespaces made available: Verify that you have the latest backups of all the tablespaces.
SET DBID <DBID>;
3
5
9
On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next.
10
On the Create Selection Set page, navigate to the source NetVault Backup Client and database, select the Whole Database node, and click Edit Plugin Options.
11
Click the Restore Options tab, and select the Check Read-Only Datafiles and Restore if Necessary and Check Read-Only Datafiles and Recover if Not Current options to include read-only datafiles in the restore and recovery process.
12
Because recovery must be performed in a disaster recovery scenario, on the Perform Recovery tab, select Perform Database Point-in-Time Recovery.
13
On the Recovery Catalog tab, clear the Use Catalog option.
14
Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択