HP 3PAR Application Software Suite for Oracle User Manual
Page 151
6.37
Recovery Manager 3.0.3/3.0.4 for Oracle User’s Guide
■
When restoring individual tablespaces or datafiles, the database can be in OPEN or
MOUNTED mode. If the database is in OPEN mode, the corresponding tablespaces must be
offline.
■
Restoring controlfiles along with datafiles and/or tablespaces is not allowed.
■
If the database is an ASM managed database, all ASM disk groups must be mounted prior
to running this command.
■
For NBU (user-managed) restore, a file named
/usr/openv/netbackup/db/altnames/
must be created on the NBU master server in order to perform
restoration to a host (including the original database host) that differs from the backup
host.
is the host name of the database server to restore.
■
Starting with Oracle 11g, a RMAN backup image of a standby database, which was backup
to local disk, cannot be restored using the
vcdba_restore
command since the backup
image cannot be seen from the Recovery Catalog from the primary (production) database.
To restore, the following steps must be performed manually:
◆
The backup image (pieces) must be manually copied from the backup host to the
primary (production) server.
◆
The backup pieces must be then cataloged manually with the Recovery Catalog from
the primary (production) server.
◆
Perform restore manually using Oracle RMAN.
Depending on the type of the virtual copy backup image (online, offline, datafile, or archonly),
corresponding database files are restored appropriately.
For NBU (user-managed) restore:
■
Control files are not restored by default.
■
For an online virtual copy, both data files and archive logs are restored unless individual
tablespaces or data files are specified. In this case, only the corresponding data files are
restored.
■
For an offline virtual copy, only data files are restored.
■
For a datafile only virtual copy, only data files are restored.
■
For an archive log virtual copy, only archive logs are restored.
For Oracle RMAN restore: