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

NetVault Plug-in for Oracle 12.3 - 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

Restoring a Duplicate Database to an alternate server with an alternate directory structure

The following procedure details the steps to restore a Duplicate Database backup to an alternate or remote server — other than where the source database resides — and use a different directory structure.

To restore a Duplicate Database backup to an alternate or remote server with an alternate directory structure, the following prerequisites must be met:

Same version of Oracle database software: The version and edition of Oracle for the destination database must be identical to the version and edition of Oracle being used for the source database. This requirement includes identical patch levels.
Duplicate Database backup available: A Duplicate Database backup must be completed successfully and made available.
Source database in open state: The source database must remain in an OPEN READ WRITE state during the entire Duplicate Database restore process.
Auxiliary instance prepared: RMAN’s backup-based Duplicate Database process requires the preparation of an auxiliary instance:
1
Oracle password file for auxiliary instance created: Required if you want to use a password file versus OS authentication for the auxiliary connection when duplicating to the same host as the source database. For more information on creating a password file, see Creating and Maintaining a Password File in the Oracle Database Administrator’s Guide.
2
Oracle Net connectivity established to auxiliary instance: The auxiliary instance must be available through Oracle Net by adding the instance to the “tnsnames.ora” file of both the source server and the alternate server. Additionally, on Windows platforms, perform the following command to start the instance:
3
Auxiliary instance destination directories exist: The following destination directories for the auxiliary instance must be created on the server where the destination database resides. If the destination database stores its datafiles in ASM, the ASM instance name for the destination database must exist.
4
PFILE created for auxiliary instance: A client-side PFILE for the Auxiliary Database must be created from the SPFILE of the source database.
Start SQL*Plus, and connect with administrator privileges to the source database.
sqlplus sys/<password>@<source_connect_identifier> AS SYSDBA
create pfile = '<PFILE_destination_directory>/
init<auxiliary_sid>.ora' from spfile;
5
PFILE updated with auxiliary values: The PFILE created for the auxiliary instance must be updated with the parameter values specific to the auxiliary instance.
Update the *.db_name= entry to reflect the name of the destination database.
*.db_file_name_convert='<source_db_create_file_dest>/
<source_sid>', '<destination_db_create_file_dest>/
<destination_sid>'
*.log_file_name_convert='<source_db_create_file_dest>/
<source_sid>', '<destination_db_create_file_dest>/
<destination_sid>'
6
Auxiliary instance started in NOMOUNT state: The auxiliary instance must be started in NOMOUNT state with the PFILE that has been updated with the parameter values specific to the auxiliary instance.
Start SQL*Plus, and connect with administrator privileges to the auxiliary instance.
sqlplus sys/<password>@<auxiliary_connect_identifier> AS SYSDBA
startup nomount pfile = '<PFILE_destination_directory>/
init<auxiliary_sid>.ora'
create spfile from pfile='<PFILE_destination_directory>/
init<auxiliary_sid>.ora';
8
Exit SQL*Plus.
You must exit SQL*Plus for the Duplicate Database restore to complete successfully.
NetVault Backup software and the Plug‑in for Oracle installed: The same version of NetVault Backup software and the plug-in must be installed and configured on the alternate server where the destination database resides.
NetVault Backup: Specify the name of the NetVault Backup Server where the source database server was added as a NetVault Backup Client.
Do Restore From NetVault Backup Server: Specify the name of the NetVault Backup Server where the source database server was added as a NetVault Backup Client.
Restore Backup taken from NetVault Backup Client: Specify the NetVault Backup Machine Name for the source database server.
Source Database Added to Plug‑in for Oracle Installed on Alternate Server: The source database must be added to the plug-in that is installed on the alternate (standby) server where the destination database resides.
For example, the production Oracle Server is named salesdb. On the alternate server that has the plug-in installed, add a database named salesdb. Complete this step even though the existing database has not yet been cloned to the alternate server. This step forces the plug-in to create a placeholder that can then be accessed during the cloning process when the Oracle database is restored to the alternate (standby) server.
For more information on adding a database, see Adding a database. These instructions work for the original database, as well as the placeholder that you create on the alternate server.
1
On the Create Restore Job — Choose Saveset page, find the applicable Duplicate Database backup, and click Next.
2
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.
3
Click the Clone Database tab, and select the Duplicate Database option.
4
In the Destination Database section:
Specify the Oracle Home for the auxiliary instance.
Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the auxiliary instance.
Specify the Oracle SYSDBA Password.
Select the Use nofilenamecheck option.
5
In the Duplicate From Database section:
Specify the Oracle SID for the source database.
Specify the Oracle Home for the source database.
Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the source database.
Specify the Oracle SYSDBA Password.
6
In the Target Client list, select the NetVault Backup Machine Name of the alternate server where the destination database resides.

Performing table-level recovery

Table-level recovery (RECOVER TABLE) is an Oracle-based feature that is available starting with Oracle Database 12.1 Enterprise Edition. If you are using the applicable version of Oracle, you can use the plug-in to recover specific Oracle tables to a specific point.

Oracle Server recovers the tablespaces that contain the tables listed for recovery into an auxiliary instance. Oracle Server then uses data pump to export the table data from the auxiliary instance to the target instance.

To restore tablespaces to the auxiliary instance, you must provide backups of the system tablespaces, the tablespaces that contain the tables to recover, and the controlfile as it existed at the time of the backup.

The plug-in lets you take advantage of the automated recovery method using an auxiliary instance. For information regarding other methods of performing table-level recovery, see your Oracle documentation. These other methods let you use the RMAN command prompt to recover from backups created by the plug-in.

The following topics provide information for performing a table-level recovery:

Uses of table-level recovery

Table-level recovery lets you recover one or more tables or table partitions to a specific point without affecting other tables or database objects. You can use backups created using the plug-in's RMAN backup method to accomplish this process. In addition to other recovery methods, table-level recovery is useful when you need to recover:

A table for which the FLASHBACK TABLE command is unavailable; for example, the Flashback Table cannot rewind because of structural changes, or the target point is older than the undo point.

Table-level requirements and limitations

There are Oracle database-specific limitations and requirements for performing this type of recovery. To perform recovery successfully, review the following requirements and limitations. For more information, including a complete list of constraints, see the table-level recovery information in your Oracle documentation.

To use automated table-level recovery, the directory specified in the “Auxiliary Destination” clause must exist before running recovery. You can use an existing empty directory, or create a directory, if the directory exists before starting the process.
You must use the CONFIGURE command to configure the channels in RMAN. The auxiliary database uses the same channels as the target database.
You cannot use the “REMAP” clause to recover tables with named NOT NULL constraints.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级