HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)

When creating an online or datafile Virtual Copy:
• If the specified database instance is a regular database, the database will be temporarily put
into backup mode before the Virtual Copy of datafile virtual volumes is created. The database
will be then taken out of backup mode. An archive log switch will be performed before Virtual
Copies of archive log virtual volumes are created.
• 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 server 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 rmora_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.
• Each database instance must be started up using either a parameter file (pfile or init.ora
file), or a server parameter file (spfile ) from default location ($ORACLE_HOME/dbs).
• If archive log mode is enabled, the datafiles and archive logs must reside on separate HP
3PAR virtual volumes.
• The online redo logs and control files should not reside on the same HP 3PAR virtual volumes
used by the datafiles and archive logs to avoid being rolled back along with datafiles and
archive logs virtual volumes. However, the online redo logs and control files can share the
separate HP 3PAR virtual volumes.
For example:
/U01 for Data
/U02 for Archive
/U03 for Control and Redo logs
• If the database files reside on Symantec 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 you use HP, Linux, or AIX LVM Volume Manager, the Oracle datafiles and archive logs must
reside on separate LVM volume groups. In addition, online redo logs and control files must
not reside on LVM volume groups that are used by Oracle datafiles and archive logs. However,
the online redo logs and control files can reside on the same LVM volume group.
• If the Oracle database is an ASM-managed database, the Oracle datafiles 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.
Recovery Manager Commands 79