3com database adapter module for networker nsr-ora v3.2 User Manual
System Administrator’s Guide
U42252-J-Z915-1-76
Recovery
Performing a recovery
5.2.3
Manual Recovery
This section describes how to completely restore a database (that is, to restore
all the tablespaces) manually (i.e. without using NSR-ORA’s automatic facilities)
and - if necessary - to a state which it had at some earlier time. We shall assume
that you are familiar with both NetWorker and ORACLE.
all the tablespaces) manually (i.e. without using NSR-ORA’s automatic facilities)
and - if necessary - to a state which it had at some earlier time. We shall assume
that you are familiar with both NetWorker and ORACLE.
ORACLE gives you the option of carrying out a recovery either offline or online.
When you perform an offline recovery the entire database has the status Mount;
this means that the database cannot be used while the recovery is in progress.
In the case of an online recovery, only those tablespaces and data files that are
currently being restored are switched offline and you can continue working with
the rest of the data. An offline recovery is generally recommended if the
tablespaces are strongly interdependent (as is the case for e.g. R/3 applica-
tions) - in this case the database will have the status Mount throughout the
recovery process. A manual offline recovery is described in the following
section.
When you perform an offline recovery the entire database has the status Mount;
this means that the database cannot be used while the recovery is in progress.
In the case of an online recovery, only those tablespaces and data files that are
currently being restored are switched offline and you can continue working with
the rest of the data. An offline recovery is generally recommended if the
tablespaces are strongly interdependent (as is the case for e.g. R/3 applica-
tions) - in this case the database will have the status Mount throughout the
recovery process. A manual offline recovery is described in the following
section.
Offline recovery of an offline or full backup
A manual offline recovery is only possible if the backup was also created offline
or using the save set ${ORACLE_SID}_full_save (full backup). When you perform
an offline recovery you can proceed as follows:
or using the save set ${ORACLE_SID}_full_save (full backup). When you perform
an offline recovery you can proceed as follows:
1. Stop the NSR-ORA archiving monitor:
# /opt/nsr/oracle/bin/start_amon.sh stop $ORACLE_SID
(on HP-UX: /opt/networker/oracle/bin/start_amon.sh stop $ORACLE_SID).
2. Shut down the database:
shutdown
3. Make sure that NetWorker does not start any other backup jobs while the
recovery is in progress, otherwise the recovery jobs and save jobs might
compete for the backup devices and so delay the restoration of the
tablespaces and redologs. For this reason you should set disabled for any
save groups that are about due to start, until the recovery has been
completed.
compete for the backup devices and so delay the restoration of the
tablespaces and redologs. For this reason you should set disabled for any
save groups that are about due to start, until the recovery has been
completed.
4. Determine all the save sets belonging to the desired full offline backup (must
be a full backup), for instance as follows:
# mminfo -v -q ´pool=<ora_pool>, savetime>="mm/dd/yy hh:mm:ss",\
savetime<="mm/dd/yy hh:mm:ss"´ -r "name,ssid"