HP 3PAR Application Software Suite for Oracle - Manual (Page 20)

For an RAC database, archive log destinations of all RAC instances must be on shared storage
(same cluster file systems or same ASM disk groups).
The Database Restoration Utility
HP 3PAR Recovery Manager Software for Oracle’s database restoration utility restores databases,
tablespaces, datafiles, or archive logs from a virtual copy's backup image. The virtual copy must
have been previously backed up using the rmora_backup command. The virtual copy must have
a backup status of Y in order to be restored. The virtual copy's backup status can be retrieved
using the Recovery Manager display utility (see
“The Virtual Copy Display Utility” (page 11) ).
For an NetBackup (user-managed) restoration, the database restoration utility can be used to restore
a virtual copy's backup image to the backup server, and it can also be used to restore to an
alternate server on an alternate mount point. For an Oracle RMAN restoration, the backup image
is always restored to the database server.
The following restrictions apply when restoring from a virtual copy's backup image:
•
When restoring the database control file (using the -c option) using Oracle RMAN, the
database must be in STARTED mode (startup nomount). In addition, restoring the database
control file along with the individual datafile or tablespace is not supported as it is not possible
to perform media recovery.
•
When restoring a database, the database must be in CLOSED or MOUNTED mode for NBU
restore or Oracle RMAN restore, respectively. For an RAC database, all RAC instances must
be in CLOSED or MOUNTED mode.
•
When restoring individual tablespaces or datafiles, the database can be OPEN, but the
corresponding tablespaces must be offline.
•
If the database is an ASM managed database, all ASM disk groups must be mounted prior
to running the restore utility.
•
For an NBU (user-managed) restoration, the
/usr/openv/netbackup/db/altnames/<database_hostname|virtual
_hostname> file must be created on the NBU master server prior to running the restore utility,
where <database_hostname|virtual_hostname> is the host name of the database
server.
Depending on the type (online, offline, datafile, or archive log) of the virtual copy's backup image,
corresponding database files are restored appropriately.
For an NBU (user-managed) restoration:
•
Control files are not restored by default.
•
For an online virtual copy, both datafiles and archive logs are restored unless individual
tablespaces or datafiles are being specified. In this case, only the corresponding datafiles are
restored.
•
Only datafiles are restored for an offline or datafile virtual copy.
•
Only archive logs are restored for an archive log virtual copy.
For an Oracle RMAN restoration:
•
Control files are not restored by default.
•
For an online virtual copy, only datafiles are restored. Archive logs are not restored to minimize
restore time as Oracle RMAN can restore only necessary archive logs during recovery.
•
Only datafiles are restored for an offline or datafile virtual copy.
•
Restoring from an archive log virtual copy backup image is not supported as Oracle RMAN
can restore necessary archive logs during recovery.
20 Overview of Recovery Manager Operations