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

About Virtual Copy Management
NOTE: HP 3PAR Recovery Manager for VMware vSphere is not functional without the HP 3PAR
Recovery Manager for VMware vSphere license. Additionally, the HP 3PAR Virtual Copy license
is required for Virtual Copy operation and the HP 3PAR Virtual Lock license is required for using
the volume retention policy. RMV will check for an existing HP 3PAR Virtual Lock license on the
storage system when a Virtual Copy is created with retention is specified.
HP 3PAR Recovery Manager for VMware vSphere allows you to take LUN-level Virtual Copies of
Virtual Machines (VMs), Datastores and Remote Copy groups. A Datastore is created on one HP
3PAR volume, and a VM is created on one or more Datastores. During VM Virtual Copy creation,
Recovery Manager for VMware vSphere will identify all the underlying HP 3PAR volumes and take
Virtual Copies simultaneously for all volumes to ensure consistency. Recovery Manager for VMware
vSphere manages this set of Virtual Copies as a single entity. Remote Copy Virtual Copies are
based at the Remote Copy group level (storage system), versus the Virtual Machine or Datastore
level (VMware perspective).
NOTE: VMware Tools must be installed on the Guest OS in order for HP 3PAR Recovery Manager
for VMware vSphere to create successful VM/Application consistent Virtual Copies. Refer to
VMware documentation for more information about VMware Tools setup instructions.
Virtual Copy Data Consistency
Several types of data consistency are possible for VM Virtual Copies and backup.
NOTE: The current version of HP 3PAR Recovery Manager for VMware vSphere supports system
crash, VM and application consistent Virtual Copies.
•
Crash Consistent - A simple virtual volume Virtual Copy without quiescing the memory blocks
inside the guest OS results in a crash consistent Virtual Copy of the VM. Data not flushed will
be lost, but all data written to the file system will be available. Sanity checking of file system
(fsck) is needed after recovery.
•
VM Consistent - All file system blocks are flushed from the memory of a VM before a Virtual
Copy is taken. This ensures that no file system data is lost if the VM crashes. Checking of file
system (fsck) is not required after recovery. No application data is flushed from memory before
the Virtual Copy is taken
•
Application Consistent - Application consistency is provided for HP 3PAR snapshots of Virtual
Machines for data compatibility with supported applications.
NOTE: A VM consistent Virtual Copy is always attempted if VMware Tools is installed on the
Guest OS. VMware must first successfully create a VMFS snapshot. For information on the best
practices and limitations of VMware snapshots, see the VMware knowledge base
http://
kb.vmware.com/ .
Virtual Copy Policy
Recovery Manager for VMware vSphere allows the creation of Virtual Copy policies for VMs
and/or Datastores. Only one policy is permitted for every VM and/or Datastore. Datastore and
VM policies exist independently; meaning a VM policy is independent of the policy of the
Datastore(s) of virtual disks it is using.
In Recovery Manager for VMware vSphere, the Virtual Copy policy contains the following attributes:
•
Maximum Number of Virtual Copy Sets - You can choose how many Virtual Copies to be
retained. When the number of Virtual Copies is at the maximum limit, the oldest Virtual Copy
is deleted when a new Virtual Copy is created.
22 Overview