Logical View Restore: Quick Restore

The Quick Restore operation is supported only in logical view, not physical view. The main purpose of Quick Restore is to recreate the file paths that were used in RMAN Cataloging.

See also. For more information about the Oracle RMAN Cataloging with Catalogic DPX, see Oracle RMAN Cataloging Control and Catalogic DPX.

Take the following steps to enable the Quick Restore:

1. In the Set Job Destinations dialog, Set the restore destination job option Oracle Restore Mode to Quick Restore. See Special Restore Destination Options for Oracle.

2. Optionally, define a directory for Quick Restore results by populating the restore destination job option Oracle Files Quick Restore Root Directory. See Special Restore Destination Options for Oracle.

Note. The restore destination node must be running the same operating system version as that of the source node.

1. Select tablespaces or database for restore. Then complete the restore steps outlined in Introduction to the Restore Functions in the Reference Guide.

When the Quick Restore operation is run, the following occurs:

• Archive logs are restored to the LOGS directory within the root directory.

• Control file is restored to the root directory.

• All covering volumes corresponding to the selected tablespace files are linked by Instant Access mapping.

• No Oracle application level processing is actually done by Catalogic DPX.

Quick Restore Structure

If the job option Oracle Files Quick Restore Root Directory is populated, its value is used as the root directory for Quick Restore operations. The mount points are rooted under that directory and the archive logs and control file are restored to that directory.

If the job option Oracle Files Quick Restore Root Directory is not populated, by default all the files and mount points are rooted under <rootdir>/BEXoracle_dbname_jobid/nodename, where:

<rootdir>	is /tmp on UNIX or Linux.
<rootdir>	is /mount on Windows.
dbname	is the name of the Oracle database.
jobid	is the 10-digit identification number assigned to the job by .
nodename	is the resolvable node name of the node where Oracle resides.

An example of a default root directory on Microsoft Windows is

E:\DPX\mount\BEXoracle_orcl_1139246458\win2k-ra

Note that this path is actually constructed during backup and the same path is used during restore.

The root directory has the following structure:

• One directory for each covering volume. For example:

  E:\DPX\mount\BEXoracle_orcl_1139246458\win2k-ra\D_\

  E:\DPX\mount\BEXoracle_orcl_1139246458\win2k-ra\E_\

• Directory LOGS containing archived logs. For example:

  E:\DPX\mount\BEXoracle_orcl_1139246458\win2k-ra\LOGS \O1_MF_1_233_1YH1F6V3_.ARC

  E:\DPX\mount\BEXoracle_orcl_1139246458\win2k-ra\LOGS \O1_MF_2_233_1YH1F6V3_.ARC

• Control_file. For example:

  E:\DPX\mount\BEXoracle_orcl_1139246458\win2k-ra\control_file

Tip. This information is identical in structure to the structure used for RMAN Cataloging. See Oracle RMAN Cataloging Control and Catalogic DPX.