Intro to VMware vVol

For awhile now, HP Storage has been working with VMware as a design partner to define and develop a VM-granular storage architecture to potentially replace vSphere’s VMFS/datastore model. This new model is called VMware Virtual Volumes (vVols). Virtual Volumes introduces a 1:1 mapping of VMs (more specifically VMDKs or VM LUNs) to storage volumes—in other words, each VM will be associated with its own, unique storage volume. With vVols we could finally have the VMDK representation in vSphere match the representation on storage.


As a result, the storage system could now have the ability to operate at the same level of granularity as vSphere, which means that vSphere could better leverage, and take advantage of, the native strengths and capabilities of modern, intelligent storage arrays, like HP 3PAR.

Why vVol?

I think the big thing VMware and storage partners like HP want to overcome is the inefficiencies and the challenges that exist today as a result of working at the LUN or volume level with vSphere. Despite all the advances that have been made, when a VM and VMDK is the unit of data management, a LUN is too coarse to gain the efficiency and flexibility customers need. The granularity mismatch between vSphere and storage systems needs to be resolved. Enter vVols.


More Information on this in HP Blogs