立即与支持人员聊天
与支持团队交流

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

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, refer to 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 file names of Control File Autobackup. The DBID is also available on the Details dialog or the Backup Contents tab.
SET DBID <DBID>;
14
Restore the SPFILE Autobackup.
If you are restoring the SPFILE to the default location, execute:
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 file names of Control File Autobackup. The DBID is also available on the Details dialog 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, execute:
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, Dell strongly 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 including 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 new 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 will record information about the restored datafiles to the Recovery Catalog. This 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 a new shared storage was configured imitating the original shared storage’s configuration.
For variations on the following disaster recovery procedure, refer to Performing Disaster Recovery in the Oracle Database Backup and Recovery Advanced User’s Guide.
Prerequisites
To perform a disaster recovery without a Recovery Catalog, the following requirements must be met:
•
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, the DBID can be obtained by examining the NetVault Backup binary logs for RMAN-based backups of the source database. The DBID is also available on the Details dialog or the Backup Contents tab.
•
Default Location for SPFILE must exist – The default location in the ASM shared storage must exist before executing the following steps. Failure to ensure that the default location exists will result 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 – Make sure that you have the latest backups of all the tablespaces.
To perform the disaster recovery
1
Start RMAN, and connect to the target database.
> rman TARGET /
2
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 file names of Control File Autobackup. The DBID is also available on the Details dialog or the Backup Contents tab.
SET DBID <DBID>;
3
Start the local instance with the FORCE NOMOUNT option.
STARTUP FORCE NOMOUNT;
4
Restore the SPFILE Autobackup.
If you are restoring the SPFILE to the default location, execute:
RUN {
ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';
RESTORE SPFILE FROM AUTOBACKUP;
}
5
Start the local instance with the FORCE NOMOUNT option.
STARTUP FORCE NOMOUNT;
6
Restore the Control File Autobackup.
If you are restoring the Control File from the last Autobackup, execute:
RUN {
ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';
RESTORE CONTROLFILE FROM AUTOBACKUP;
}
7
Mount the database:
ALTER DATABASE MOUNT;
8
Disable Block Change Tracking.
SQL "ALTER DATABASE DISABLE BLOCK CHANGE TRACKING";
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.
PIT Recovery recovers the database to a specific time, log sequence number, or SCN. If the specific time or log sequence of the failure is not known, Dell recommends that you use the SCN option.
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.
RMAN will automatically choose the best available full, incremental, or Archived Log backups and restore and recover the database.
15
In RMAN, enable Block Change Tracking.
SQL "ALTER DATABASE ENABLE BLOCK CHANGE TRACKING";
16
Update the RMAN metadata.
CROSSCHECK ARCHIVELOG ALL;
17
Exit RMAN.
18
Start all RAC instances.
>srvctl START DATABASE -d <database_name>
19
Start all RAC Services.
>srvctl START SERVICE -d <database_name>
20
Ensure that all RAC instances are running.
>srvctl STATUS DATABASE -d <database_name>
 
 
*IMPORTANT: After completing a disaster recovery, Dell strongly recommends that you perform a Full or Incremental Level 0 backup with the entire database selected on the NetVault Backup Selections page.

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 Plug‑in for Oracle is installed, the plug-in must be relocated 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 Plug‑in for Oracle is installed 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 a 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.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级