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

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.
Recovery Manager for Oracle with Oracle Standby Database
All HP 3PAR Recovery Manager Software for Oracle’s utilities can be run against an Oracle
physical standby database instead of the production database. This completely eliminates the
performance impact on the production database.
In addition to the current Recovery Manager for Oracle’s limitations and restrictions when running
against an Oracle primary database, the following limitations and restrictions apply when running
against an Oracle physical standby database:
•
Only Oracle 10g and 11g are supported.
•
A standby database must be a physical standby database. Logical and snapshot standby
databases are not supported.
•
If using Oracle RMAN for backup, the primary database, and not the standby database, must
be registered with Oracle Recovery Catalog.
•
A snapshot of a standby database can be used to promote back to the standby database
volumes, but it cannot be used to promote back to the primary database volumes.
•
Oracle parameter file and control file are not compatible between the standby database and
the primary database. They cannot be used to restore to the primary database unless Oracle
RMAN (11g) is used for restoring. This means that the Oracle parameter file and control file
of the primary database must be backed up manually outside of the Recovery Manager for
Oracle.
Recovery Manager for Oracle and Autonomic Groups
HP 3PAR Autonomic Groups allow domains, hosts, and virtual volumes to be grouped into a set
that is managed as a single object. HP 3PAR Recovery Manager Software for Oracle supports
domain sets, and can coexist with host sets and volume sets. Refer to the HP 3PAR OS Concepts
Guide for additional information about 3PAR Autonomic Groups.
Recovery Manager for Oracle and Domain Sets
HP 3PAR Recovery Manager Software for Oracle allows the management of multiple database
servers belonging to different virtual domains from a single backup server.
Recovery Manager for Oracle with Oracle Standby Database 21