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

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 earlier than 10.2.0.5 or 11.0.1.7, if an ASM instance is up on the
backup server, the mount utility checks if there is any mounted diskgroup. If there is no
mounted diskgroup, 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
are 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 earlier than 10.2.0.5 or 11.1.0.7,
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 LVM volume groups and their logical volumes if the database files reside
on LVM logical volumes.
•
Deports the read-write Virtual Copy from the backup server.
•
Removes the read-write Virtual Copy.
NOTE: rmora_umount will remove all the changes in the cloned database.
The Virtual Copy Export Utility
The Virtual Copy export utility of HP 3PAR Recovery Manager Software for Oracle exports an
existing Virtual Copy to an alternate backup server (rmora_export command). The exported
Virtual Copy can then be mounted, backed up or cloned at the alternate backup server.
The Virtual Copy must have Available status in order to be exported. An alternate backup server
must have the same operating system, file system, volume manager, and Recovery Manager for
Oracle version as the current backup server. Status of a Virtual Copy can be obtained using a
display utility such as the rmora_display command.
The following restrictions apply to exporting Virtual Copies:
•
If Symantec Volume Manager is used, the alternate backup server must have the same version
of Symantec Volume Manager that is currently installed.
•
The alternate backup server must be connected to the same HP 3PAR StoreServ Storage system
as the current backup server.
•
SSH must be configured to access the alternate backup server, the NetBackup master server,
and any other related servers, from the current backup server without prompting for a pass
phrase. For more information, see
“Setting Up SSH Connections for Recovery Manager” (page
39) .
Recovery Manager for Oracle Utilities 15