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

NOTE: The ASM major release version on the backup server must be higher than the ASM
major release 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 LVM volume groups are imported and all corresponding LVM snapshot
volumes are activated if the database files reside on HP LVM 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
HP 3PAR Recovery Manager Software for Oracle’s virtual copy unmount utility (rmora_umount)
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.
Unmounting a database virtual copy involves the following actions:
•
For an ASM-managed database, if the ASM database on the backup server has a version at
or above 10.2.0.5 or 11.1.0.7, unmounting the virtual copy drops the ASM diskgroups that
are contained in the virtual copy and cleans up the ASM disks.
•
If the ASM database on the backup server has versions lower than those listed in the previous
bullet, unmounting shuts down the ASM instance and cleans up ASM disks.
•
Unmounts all snapshot file systems if the database files reside on file systems.
•
Destroys all snapshot VxVM disk groups and their VxVM volumes if the database files reside
on VxVM volumes.
•
Destroys all snapshot HP LVM volume groups and their LVM volumes if the database files
reside on LVM volumes.
Recovery Manager for Oracle Utilities 13