지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Retrieving a Control File manually

When Control File Autobackups are not available, the RMAN Catalog is not used, and only Control File backups were performed by selecting the Control File node on the NetVault Backup Selections page, you might be able to use the following procedure to extract the Control File from a backup piece.
To recover the most recent (or other, as required) Control File manually from a backup piece
1
On the Create Restore Job - Choose Saveset page, find the latest available backup that is marked with “Controlfile Included.”
2
Recover the Control File.
SQL> STARTUP NOMOUNT;
DECLARE
devtype varchar2(256);
done    boolean;
BEGIN
devtype := dbms_backup_restore.deviceallocate('sbt_tape', params=>'');
dbms_backup_restore.restoresetdatafile;
dbms_backup_restore.restorecontrolfileto
('<destination PathAndNameOfControlFile>');
dbms_backup_restore.restorebackuppiece
('<backupSegment NameIdentifiedEarlier>',done=>done);
END;
/
For example:
sqlplus /nolog
connect / as sysdba
STARTUP NOMOUNT;
DECLARE
devtype varchar2(256);
done    boolean;
BEGIN
devtype := dbms_backup_restore.deviceallocate('sbt_tape', params=>'');
dbms_backup_restore.restoresetdatafile;
dbms_backup_restore.restorecontrolfileto
('C:\oracle\product\10.1.0\oradata\o10gg\control01.ctl');
dbms_backup_restore.restorebackuppiece
('ZETK2003:#3293:ZETK2003:274_578391288:O10GG_1135958971',done=>done);
END;
/
3
Use the replicate controlfile command to copy the restored Control File.
RMAN TARGET / NOCATALOG
SET DBID <Source_DBID>;
connect TARGET /
RUN {
ALLOCATE CHANNEL C1 TYPE 'SBT_TAPE';
replicate controlfile from
'<sourcePathAndNameOfControlFile>';
}

Using advanced procedures with RMAN restores

This section contains sections that describe other restore operations that can be performed with Plug‑in for Oracle.
•
Renaming or relocating files (or both)
•
Duplicating a database in a non-RAC environment
•
Performing table-level recovery
Renaming or relocating files (or both)
With the RMAN backup method, the plug-in lets you rename the Control File and datafiles during restore. Renaming files can be useful if you do not want to overwrite the existing version and want to create a copy of the file. You can also relocate the files to a different directory while restoring it with the plug-in.
To rename or relocate files during restore
1
Complete the steps outlined in Preparing the database for recovery.
2
In the Navigation pane, click Create Restore Job, select Plug‑in for Oracle from the Plugin Type list.
3
In the saveset table, select the applicable item, and click Next.
For more information, see Selecting data for a restore.
4
On the Create Selection Set page, select the datafile or Control File to be restored.
5
From the Actions list, select Rename.
6
In the Rename/Relocate dialog, enter the applicable information.
•
Rename – Enter the new name.
•
Relocate – Enter the new path.
The plug-in uses the set newname RMAN command to restore/rename RMAN backups. The set newname command has precedence over the DB_CREATE_FILE_DEST parameter. If the full path is not specified for a restore or rename, the plug-in behaves as follows:
•
SPFILE – The file is restored to the “$ORACLE_HOME/dbs” directory with the new name.
•
Datafile –
•
If you specify a new location when the file is created, the file is restored/renamed to this location with the new name.
•
If you do not specify a new location when the file is created, the file is restored/renamed to “$ORACLE_HOME/dbs” with the new name.
 
 
*NOTE: A full path can include a path to an ASM location. For example: +DATA/my_db/my_datafile_renamed.dbf
When renaming the Control File during restore, the resulting file name should exist in the CONTROL_FILES list in the Oracle Parameter File.
7
Click Ok to apply changes.
The item is accompanied by the rename/relocate information in parenthesis.
8
Continue with the restore procedure as explained in Finalizing and submitting a job.

Duplicating a database in a non-RAC environment

A Duplicate Database backup lets the DBA create a duplicate or clone of a source database for special purposes that will not affect the overall backup and restore procedures for the source database. RMAN supports duplicating databases to increase a DBA’s flexibility when performing the following tasks:
•
Testing backup and recovery procedures.
•
Testing an upgrade to a new release of Oracle Database.
•
Testing the effect of applications on database performance.
•
Generating reports.
For more information on duplicating a multi-instance RAC database, see Duplicating a database in a RAC environment. For more information on Oracle’s Duplicate Database functionality, refer to Duplicating a Database in the Oracle Database Backup and Recovery User’s Guide.
The plug-in provides the following restore scenarios for the Duplicate Database backup:
•
Restoring a Duplicate Database to the same server
•
Restoring a Duplicate Database to an alternate server with the same directory structure
•
Restoring a Duplicate Database to an alternate server with an alternate directory structure

Restoring a Duplicate Database to the same server

The following procedure details the steps to restore a Duplicate Database backup to the local or same server where the source database resides. Because the duplicated database or destination database will reside on the same physical server as the source database, the destination database must use a different directory structure.
To restore a Duplicate Database backup to the same server, 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 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, refer to 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. Additionally, on Windows platforms, perform the following command to start the instance:
oradim -new -sid <sid_name>
3
Auxiliary instance destination directories exist – The following destination directories for the auxiliary instance must be created on the server where the destination database will reside. If the destination database will store its datafiles in ASM, the ASM instance name for the destination database must exist.
•
Control_Files
•
DB_Create_File_Dest
•
Audit_File_Dest
•
Background_Dump_Dest
•
User_Dump_Dest
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 a PFILE from the SPFILE.
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.
•
Remove all entries that begin with: <source_sid>.__
•
Update the *.db_name= entry to reflect the name of the destination database.
•
Update the following entries to reflect the destination directory for the auxiliary instance. This directory must exist; however, if the source database stores the datafiles in ASM, the ASM instance name for the destination database should be specified for each of the following control_files and db_create_file_dest parameters:
*.audit_file_dest=
*.background_dump_dest=
*.control_files=
*.user_dump_dest=
*.db_create_file_dest=
*.db_recovery_file_dest=
•
Comment out the following entry by inserting a “#” (number sign) at the beginning of the following entry:
*.dispatchers='(PROTOCOL=TCP) (SERVICE=<source_sid>XDB)'
•
Add the following line to specify the pairs of strings for converting the names of datafiles and tempfiles.
*.db_file_name_convert='<source_db_create_file_dest>/<source_sid>',
'<destination_db_create_file_dest>/<destination_sid>'
For example:
*.db_file_name_convert=' C:\oracle\oradata\prod',
'c:\oracle\oradata\test'
•
Add the following line to specify the pairs of strings for naming online redo log files:
*.log_file_name_convert='<source_db_create_file_dest>/
<source_sid>', '<destination_db_create_file_dest>/
<destination_sid>'
For example:
*.log_file_name_convert=' C:\oracle\oradata\prod',
'c:\oracle\oradata\test'
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
•
Start the instance in NOMOUNT state.
startup nomount pfile = '<PFILE_destination_directory>/
init<auxiliary_sid>.ora'
7
Auxiliary instance created from SPFILE from the PFILE
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.
To restore the Duplicate Database
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 Net Service name of the auxiliary instance in the Target Service field.
•
Specify the Oracle Home for the auxiliary instance.
•
Specify the Oracle SYSDBA User Name that will be used by the plug-in to connect to the auxiliary instance.
•
Specify the Oracle SYSDBA Password.
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 will be used by the plug-in to connect to the source database.
•
Specify the Oracle SYSDBA Password.
6
Continue with the restore procedure, including completion of the Schedule and Advanced Options lists, as explained in Finalizing and submitting a job.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택