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

2.10 Recovery Manager Utilities
Recovery Manager 3.0.3/3.0.4 for Oracle User’s Guide
2.6.4 The Virtual Copy Mount Utility
3PAR Recovery Manager’s mount utility mounts an existing database virtual copy that was
created using the create utility on the backup host using the vcdba_mount command. The
mounted virtual copy can be used for off-host processing purposes such as backup or database
cloning.
The following restrictions apply when mounting a database virtual copy:
■ The virtual copy must have an Available or Mounted(P) status in order to be mounted.
The virtual copy's status can be retrieved using the Recovery Manager display utility.
■ The same virtual copy cannot be mounted concurrently at different mount points.
■ If the database files reside on Veritas VxVM Volumes, only one virtual copy per database
can be mounted at any time on the backup host. This is due to the VxVM disk groups from
different virtual copies of the same database having the same names and so cannot be
imported at the same time.
■ If the database files reside on ASM disk groups, it is dependent on which ASM database
version is installed on the backup host, different restrictions apply as follows:
◆ If the ASM version on the backup host is 10.2.0.5 or 11.1.0.7, one virtual copy per
database can be mounted at any time on the backup host. However, virtual copies from
different databases can be mounted concurrently.
◆ If the ASM version on the backup host is lower than the releases mentioned in the
previous bullet, only one virtual copy can be mounted at any time on the backup host.
This restriction prevents an Oracle ASM instance on the backup host from hanging due
to some ASM's idle processes still holding a virtual copy's devices, even though the
corresponding ASM disk groups are dropped.
■ If the database files reside on OCFS2 file systems, only one virtual copy per database can be
mounted at any time on the backup host.
Mounting a database virtual copy involves the following actions:
■ A read-write virtual copy of the original (read-only) virtual copy is created.
■ The read-write virtual copy is imported to the backup host.
■ Snapshots of Veritas VxVM disk groups are imported and all corresponding snapshot VxVM
volumes are started if the database files reside on VxVM volumes.
■ All snapshot file systems are mounted if the database files reside on file systems.