Table of Contents
Advertisement
When the variable points to a valid location, the restore through the GUI will save the RMAN restore
script to the specified location and it will not execute the restore. Once the script has been saved, it
can be edited and changed. Afterwards, you can start it from RMAN directly.
OB2RMANSAVE=/opt/oracle/
Once the script has been saved, it can be edited and changed. Afterwards, you can start it from
RMAN directly as shown below:
$ rman target / catalog rman/xxx@RCVCAT cmdfile rman_script.rcv
Note: as this functionality is not part of the DP 6.0 General Release, you need to contact Data
Protector Support to receive the patch which enables it. This enhancement is available for all
supported platforms.
Note: After executing the restore, remember to clear the OB2RMANSAVE variable; as long as it is
saved, the RMAN restores will not be performed, but only the RMAN script will be saved.
Oracle Restore Configuration
The same way we distribute our backup load over the available instances in the Cluster, it may also
be advisable to do it at restore time. However, in this case, the choice of using a Service to configure
the restore will not necessarily be the faster option.
As it has been seen for the Backup, if we allocate the channels manually on the instances, we obtain,
in general, the best performance results. Therefore, for performance purposes, in a restore scenario,
the recommendation is to edit an RMAN restore script.
Consider the following situation: the backup session we want to restore was performed using the
Oracle service MSL5000 (Backup session 4). During the backup, two RMAN channels were allocated
on RAC2 (ita021).
For the restore however, instead of connecting through a service, we would like to have instances
RAC1 and RAC2 running the restore with one channel each.
As described in the above section, we can have Data Protector writing the RMAN Restore script to a
local directory, without running the restore. First, decide the number the channels to be used (the
same as in the backup, one per tape device is recommended) and include the connection string at the
end of the parameter specification (see example below)
Important Note: the OB2BARLIST channel parameter, which points to the backup specification and
includes the tape drives and concurrency to be used, should match your needs. If not, edit before the
backup specification.
In the example below, we used two instances and two tape drives for the backup; it is recommended
to use the same concurrency as in the backup session. The example is performed for the restore and
recovery of the POOL tablespace.
For the backup we allocated two channels (RAC1 and RAC2) manually.
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=RAC,OB2BARLIST=RAC_POOL_man_ch_1_2)' connect sys/xxx@RAC1;
allocate channel 'dev_1' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=RAC,OB2BARLIST=RAC_POOL_man_ch_1_2)' connect sys/xxx@RAC2;
SQL " alter tablespace POOL offline immediate";
restore tablespace 'POOL';
recover tablespace 'POOL';
SQL " alter tablespace POOL online";
release channel 'dev_0';
release channel 'dev_1';
}
24
Hide quick links:
Advertisement
Table of Contents
