3PAR Management
■Application Consistent - Application consistency is provided for 3PAR snapshots of Virtual Machines for data compatibility with supported applications.
2.7.2Virtual 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’s 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. Once this limit is reached, the earliest virtual copy will be deleted to allow the latest virtual copy to be created.
■Enable expirable virtual copies - Allows you to specify that created virtual copies are removed according to a specified schedule and are not affected by the maximum count.
■Retain Virtual Copy Set - The supported number of hours, days, weeks, months, and years that a virtual copy set is retained.
NOTE: The Retain Virtual Copy Set option requires the 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 OS’s.
2.7.3Datastore Virtual Copies
A datastore is created on a Fibre Channel or iSCSI LUN. During virtual copy creation, Recovery Manager for VMware vSphere identifies the 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 3PAR volume. A datastore that spans across more than one LUN is not supported.
About Virtual Copy Management
2.23
