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

•
If the database files reside on ASM disk groups, it is dependent on which ASM database
version is installed on the backup server, different restrictions apply as follows:
◦ If the ASM version on the backup server is 10.2.0.5 or 11.1.0.7 and above, one Virtual
Copy per database can be mounted at any time on the backup server. However, Virtual
Copies from different databases can be mounted concurrently.
◦ If the ASM version on the backup server is lower than the releases mentioned in the
previous bullet, only one Virtual Copy can be mounted at any time on the backup server.
This restriction prevents an Oracle ASM instance on the backup server 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.
NOTE: The ASM version on the backup server must be equal or higher than the ASM version
on the database server.
•
On Linux systems, if the database files reside on OCFS2 1.4.1 or above file systems, Recovery
Manager for Oracle supports multiple Virtual Copies per database being mounted at the same
time. For versions lower than OCFS2 1.4.1, only one Virtual Copy per database can be
mounted at any time on the backup server.
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 server.
•
Snapshots of Symantec VxVM disk groups are imported and all corresponding snapshot VxVM
volumes are started if the database files reside on VxVM volumes.
•
Snapshots of HP or Linux LVM volume groups are imported and all corresponding LVM snapshot
volumes are activated if the database files reside on LVM logical volumes.
•
All snapshot file systems are mounted if the database files reside on file systems.
•
For Virtual Copies from an ASM-managed database, based on the different ASM database
releases on the backup server, the operation is different.
◦ For ASM versions 10.2.0.5 or 11.0.1.7 and above, if an ASM instance exists and is up
on the backup server, then all diskgroups from the Virtual Copy are mounted in this ASM
instance. If no ASM instance is up on the backup server, , an ASM instance is started up
on the backup server, and all ASM disk groups in the Virtual Copy are mounted.
◦ For ASM versions lower than the releases mentioned in the previous bullet, if an ASM
instance is up on the backup server, the mount utility checks if there is any mounted
diskgroup. If none, the ASM instance is shut down, otherwise, the mount utility gives an
error and exits. If there are no errors, a new ASM instance is started up and all diskgroups
contained in the current Virtual Copy are mounted.
The Virtual Copy Unmount Utility
The Virtual Copy unmount utility (rmora_umount) of HP 3PAR Recovery Manager Software for
Oracle unmounts the file system where a Virtual Copy is currently mounted, or drops ASM disk
groups if ASM is used. The read-write Virtual Copy is removed, as well as any components that
were created during the mount Virtual Copy stage.
The Virtual Copy must have Mounted or Mounted(P) status in order to be unmounted. The status
of a Virtual Copy can be obtained using a display utility such as the rmora_display command.
Recovery Manager for Oracle Utilities 13