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

2.11 Recovery Manager Utilities
Recovery Manager for Oracle User’s Guide
■ For virtual copies from an ASM-managed database, based on the different ASM database
releases on the backup host, the operation is different.
◆ For ASM versions 10.2.0.5 or 11.0.1.7, if an ASM instance exists and is up on the backup
host, then all diskgroups from the virtual copy are mounted in this ASM instance.
Otherwise, an ASM instance is started up on the backup host, 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 host, 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. After that, a new ASM instance is started up and all diskgroups
contained in the current virtual copy are mounted.
2.6.5 The Virtual Copy Unmount Utility
3PAR Recovery Manager’s virtual copy unmount utility ( vcdba_umount ) unmounts the file
system where a virtual copy is currently mounted. 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 vcdba_display
command.
Unmounting a database virtual copy involves the following actions:
■ For an ASM-managed database, if the ASM database on the backup host 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 host 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.
■ Deports the read-write virtual copy from the backup host.
■ Removes the read-write virtual copy.