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

NOTE: The Retain Virtual Copy Set option requires the HP 3PAR Virtual Lock license. Contact
your local service provider for additional information.
•
Ensure Application Consistency - This option is used to create virtual copies that adhere to
data format standards used by Microsoft VSS for guest operating systems. This option is only
available VM policy.
Datastore Virtual Copies
A datastore is created on a Fibre Channel or iSCSI LUN. During virtual copy creation, Recovery
Manager for VMware vSphere identifies the HP 3PAR volume used and takes a virtual copy of the
volume. Recovery Manager for VMware vSphere stores the details of all virtual disks and VMs
present in the datastore.
This feature has the following restrictions:
•
The datastore must be on exactly one HP 3PAR volume. A datastore that spans across more
than one LUN is not supported.
•
RDM LUNs defined in the datastore are not included in the virtual copy. It is possible that a
HP 3PAR LUN is used as RDM in a guest OS, which is defined in a datastore created on
another HP 3PAR LUN.
NOTE: A virtual copy of a datastore does not include any RDM 3PAR LUNs.
•
All datastore virtual copies can be VM or crash consistent. File system and/or application
integrity checks must be performed in the guest OS for the crash consistent virtual copies after
restoration.
•
Network File System (NFS) datastores are not supported.
•
VMFS file systems spanning multiple hard disk partitions to create a single logical volume are
not supported.
•
The datastore must not be on an ESX SAN boot disk. Virtual Copy operations are not supported
on datastores residing in ESX SAN boot disks.
For information about creating virtual copies, see “Creating New Virtual Copies” (page 62) .
Virtual Machine Virtual Copies
A Virtual Machine (VM) configuration files are created in a datastore. VMDK virtual disks used by
VMs are created on one or more datastores. In addition, a VM can use HP 3PAR volumes directly
as RDM virtual disks. Recovery Manager for VMware vSphere identifies all of the HP 3PAR volumes
used by a VM and creates virtual copies of all of them simultaneously. A list of virtual disk names
and their type (RDM or VMDK) and configuration file name are also recorded in the repository
during virtual copy creation.
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 21) .
•
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.
About Virtual Copy Management 21