Recovery set data consistency, Recovery set policy, Datastore recovery sets – HP 3PAR Application Software Suite for VMware User Manual
Page 15
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 Recovery Sets. Refer to VMware
documentation for more information about VMware Tools setup instructions.
Recovery Set data consistency
Several types of data consistency are possible for VM Recovery Sets and backup.
NOTE:
The current version of HP 3PAR Recovery Manager for VMware vSphere supports system
crash, VM and application consistent Recovery Sets.
•
Crash Consistent—A simple virtual volume Recovery Set without quiescing the memory blocks
inside the guest OS results in a crash consistent Recovery Set 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 Recovery
Set 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 Recovery Set 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 Recovery Set 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
.
Recovery Set policy
Recovery Manager for VMware vSphere allows the creation of Recovery Set 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 Recovery Set policy contains the following attributes:
•
Maximum Number of Recovery Sets - You can choose how many Recovery Sets to be retained.
When the number of Recovery Sets is at the maximum limit, the oldest Recovery Set is deleted
when a new Recovery Set is created.
•
Enable expirable Recovery Sets - Allows you to specify that created Recovery Sets are removed
according to a specified schedule and are not affected by the maximum count.
•
Retain Recovery Set - The supported number of hours and days that a Recovery Set is retained.
NOTE:
The Retain Recovery Set option requires the HP 3PAR Virtual Lock license. RMV will
check for an existing HP 3PAR Virtual Lock license on the storage system when a Recovery
Set is created with retention is specified. Contact your local service provider for additional
information.
•
Ensure Application Consistency - This option is used to create Recovery Sets that adhere to
data format standards used by Microsoft VSS for guest operating systems. This option is
available for Virtual Machine and Datastore with Virtual Machines.
Datastore Recovery Sets
A Datastore is created on a Fibre Channel or iSCSI LUN. During Recovery Set creation, Recovery
Manager for VMware vSphere identifies the HP 3PAR volume used and takes a Recovery Set of
Recovery Set management
15