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

A VM Virtual Copy has the following restrictions:
•
Virtual disks used by a VM must be from the HP 3PAR Datastore, and the latter must satisfy
the conditions mentioned in
“Datastore Virtual Copies” (page 23) .
•
If the VM uses more than one HP 3PAR volume, all of them must be from the same HP 3PAR
storage array.
•
VMs that use a mix of HP 3PAR LUNs and third party LUNs are not supported.
•
All VM Virtual Copies can be VM or crash consistent. File system and/or application integrity
checks must be performed in the guest OS after restoration for the crash consistent Virtual
Copies.
•
VMs using NFS Datastores are not permitted.
•
VMFS file systems spanning multiple hard disk partitions to create a single logical volume are
not supported.
For information about creating VM Virtual Copies, see “Creating New Virtual Copies” (page 70) .
Remote Virtual Copies
Remote Virtual Copies are based on the Remote Copy Group. If a VM or Datastore uses virtual
volumes outside of the Remote Copy group, HP 3PAR Recovery Manager for VMware vSphere
cannot take a remote Virtual Copy of the group. Remote Virtual Copies require a remote host with
TCP/IP connectivity to the target Storage System.
•
VMs or Datastores must be contained within the Remote Copy group
•
Restore processes are currently performed manually
The Virtual Copy Browser
NOTE: You must have an HP 3PAR Recovery Manager for VMware vSphere license in order to
use the Virtual Copy browser.
In Recovery Manager for VMware vSphere, every Virtual Copy, VM, or Datastore has its own
metadata, which is used in instances where a restoration is necessary. Metadata is kept in a local
file system of the server.
You can view Virtual Copy metadata at any time after it was created using the Virtual Copy browser
of the VM and Datastore views of the plug-in.
24 Overview