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

6.15
Recovery Manager 3.0.3/3.0.4 for Oracle User’s Guide
■ If the specified database instance is a physical standby database, the database will be
temporarily taken out of managed recovery mode before the virtual copy of the datafile
virtual volumes is created. The database will then be put back into the original managed
recovery mode.
A datafile virtual copy alone cannot be used to restore and recover the database. An archive
log virtual copy can be used in conjunction with an online virtual copy to simulate an
incremental backup.
Once created, the virtual copy can be mounted on the backup host for off-host processing
purposes such as backup and database cloning. If the virtual copy will be backed up using
Oracle RMAN, the primary database (not the standby database) must be registered with the
Oracle Recovery Catalog Database.
To use the vcdba_create command, the Oracle database structure must satisfy the following
requirements:
■ The database must be running in archive log mode and automatic archival must be enabled
in order to create an online, datafile, or archive log virtual copy.
■ If archive log mode is enabled, the data files and archive logs must reside on separate 3PAR
virtual volumes.
■ The online redo logs and control files should not reside on the same 3PAR virtual volumes
used by the data files and archive logs to avoid being restored when using Recovery
Manager Rollback feature. However, the online redo logs and control files can share the
same 3PAR virtual volumes.
■ If the database files reside on Veritas VxVM volumes, the datafiles and archive logs must
reside on separate VxVM disk groups. The online redo logs and control files should reside
on separate VxVM volumes used by the datafiles and archive logs.
■ If the Oracle database is an ASM-managed database, the data files and archive logs must
reside on separate ASM disk groups. The online redo logs and control files should not
reside on the same ASM disk groups used by the datafiles and archive logs to avoid being
restored when using the Recovery Manager Rollback feature. In addition, ASM disk groups
should not be shared between different databases.
■ If the Oracle database is an RAC database, all RAC instances must share the same archive
log destinations (i.e., the same cluster file system or the same ASM disk groups).