beautypg.com

6 vmfs snapshots, Vmfs snapshots – HP 3PAR Application Software Suite for VMware User Manual

Page 36

background image

2.26

About Virtual Copy Management

3PAR Management Plug-In and Recovery Manager 2.1.0 for VMware vSphere User’s Guide

The virtual copy set name (optional).

The number of virtual copy volumes in the virtual copy.

A list of pairs (source volume, virtual copy volume). Each pair can have a list of virtual disks

and/or VM names.

All virtual copies are organized in the browser based on their creation times. The browser

displays all relevant metadata so that you can make restore decisions faster and without

actually mounting virtual copy volumes.

The data shown in the virtual copy browser comes from the metadata repository and may not

reflect the current state of InServ Storage Server. It is possible that volumes shown in the

browser may not exist in the InServ Storage Server; for example, if a volume is deleted.

For information about viewing the Virtual Copy browser, see

Figure 5-12. Viewing the Alerts

on page 5.12.

2.7.6 VMFS Snapshots

In order to maintain a VM consistent virtual copy, a VMFS snapshot will be created before

creating a 3PAR virtual copy and the VMFS copy will be deleted when the 3PAR virtual copy is

created. 3PAR virtual copies and VMFS snapshots cannot coexist. 3PAR virtual copy creation will

fail if there are pre-existing VMFS snapshots for the VM.

NOTE: In order to maintain a VM consistent virtual copy, a VMFS snapshot will be

created before creating a 3PAR virtual copy and the VMFS copy will be deleted

when the 3PAR virtual copy is created. 3PAR virtual copies and VMFS snapshots

cannot coexist. 3PAR virtual copy creation will fail if there are pre-existing VMFS

snapshots for the VM.

When creating a VMFS snapshot, VMware can fail the operation with the

message: “Cannot create a quiesced snapshot because the create snapshot

operation exceeded the time limit for holding off I/O in the frozen virtual

machine.”

If this message is displayed, the VMware Tools process should be restarted, or

reinstalled to resolve the issue.