HP 3PAR Application Software Suite for VMware - Manual (Page 72)

3. Select the Virtual Copy to mount from the Virtual Copy Set list.
4. Right-click the Virtual Copy in the Virtual Copy table.
A menu appears providing two mount choices:
•
Mount on ESX host as Datastore on - Select from a list of ESX/ESX(i) hosts managed by
the vCenter Server that share access to the HP 3PAR StoreServ Storage system.
•
Mount on Proxy Host - Select from a list of hosts not managed by the vCenter Server, but
which have access to the HP 3PAR StoreServ Storage system.
NOTE: For ESX 3.5, the LVM.EnableResignature parameter must be set to 1 to allow mount
operations. The parameter can be found in the ESX host Configuration, Advanced Settings,
and LVM options.
5. Click the mount type and then select an ESX host or Proxy Host from the menu that appears.
The Confirm dialog box appears.
6. Click OK.
The Virtual Copy mount task is submitted and a message indicates that the request is being
processed.
You can check the status column to see that the Virtual Copy has been mounted.
Unmounting Virtual Copies
NOTE: Recovery Manager for VMware vSphere does not check if the volume being unmounted
is in use. Ensure that the volume is inactive prior to unmounting.
To unmount a previously mounted Virtual Copy:
1.
Follow the instructions in “Viewing Virtual Copy Information” (page 68) .
2. Click the Virtual Copies tab.
3. Select the Virtual Copy you wish to unmount from the Virtual Copy Set list.
4. Right-click the mounted Virtual Copy in the Virtual Copy table.
5. Click Unmount and then select the host.
The Confirm dialog box appears.
6. Click OK. A message indicates that the request is being processed and the mounted copy is
unmounted.
Restoring Datastores by Promoting a Virtual Copy
Normal restore scenarios involve restoring virtual disk images. In a VMFS Datastore, there can be
many virtual disks. Typically, you can identify the virtual disk to be restored and copy it over the
old one. However, in some cases the virtual machine file system may be corrupted and all virtual
disks need to be replaced. In such scenarios, promote one of the Virtual Copies to a base volume.
The HP 3PAR Operating System Software supports a non-disruptive Virtual Volume conversion from
a fully to thinly-provisioned or thinly to fully-provisioned Virtual Volume. Recovery Manager for
VMware limits the promotion of a Virtual Copy taken before a Virtual Volume conversion. A popup
message box with error message displays if the action occurs. Performing any RMV Virtual Copy
operations such as creating or deleting must only occur after a Virtual Volume conversion is
completed.
NOTE: After a Virtual Volume conversion is complete, also update the Recovery Manager Cache
to see changes if you are already logged on to the session. The RMV server does not notify the
RMV plug-in for backend data changes.
72 Working with Virtual Copies