Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for Oracle 12.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 Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs) Troubleshooting

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.

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 SQL*Plus, and connect with administrator privileges to the local instance.
SQLPLUS SYS AS SYSDBA
12
In SQL*Plus, start the local instance with the MOUNT option.
STARTUP MOUNT;
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.
•
To delete the restored archive logs that Oracle deems unnecessary, select the Delete Archive Logs No Longer Needed option.
16
To perform recovery on the database, that is, to reconstruct the database up to the current or specified point, select one of the following options on the Perform Recovery tab:
•
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.
RMAN automatically chooses the best available full, incremental, or Archived Log backups, and restores and recovers the database.
19
From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed.
20
Start SQL*Plus, and connect with administrator privileges to the local instance.
SQLPLUS SYS AS SYSDBA
21
Enable the CLUSTER_DATABASE initialization parameter for the local instance.
ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=SPFILE SID='<local_SID>';
22
Shut down the local instance.
SHUTDOWN ABORT;
23
Exit SQL*Plus.
24
Start all RAC instances.
>srvctl START DATABASE -d <database_name>
25
Start all RAC Services.
>srvctl START SERVICE -d <database_name>
26
Ensure that all RAC instances are running.
>srvctl STATUS DATABASE -d <database_name>
 
* 
IMPORTANT: After completing a restore of the Whole Database, Quest recommends that you perform a Full or Incremental Level 0 backup with the entire database selected on the NetVault Backup Selections page.

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.

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 filenames of Control File Autobackup. The DBID is also available on the Details dialog box or the Backup Contents tab.
SET DBID <DBID>;
14
Restore the SPFILE Autobackup.
If you are restoring the SPFILE to the default location, run:
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 filenames of Control File Autobackup. The DBID is also available on the Details dialog box 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, run:
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, Quest 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; the minimum includes 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 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 records information about the restored datafiles to the Recovery Catalog. This recording 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 new shared storage was configured imitating the original shared storage’s configuration.

For variations on the following disaster recovery procedure, see Performing Disaster Recovery in the Oracle Database Backup and Recovery Advanced User’s Guide.

•
Prerequisites
•
Performing the disaster recovery
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione