With Virtual Volumes (VVols), available with vSphere 6.0 or a later release, an individual virtual machine, not the datastore, becomes a unit of storage management. The storage hardware gains control over virtual disk content, layout, and management.
With Virtual Volumes, abstract storage containers replace traditional storage volumes based on LUNs or NFS shares. Virtual Volumes maps virtual disks and their derivatives, clones, snapshots, and replicas, directly to objects, called virtual volumes, on a storage system. This mapping allows vSphere to offload intensive storage operations such as snapshoting, cloning, and replication to the storage system. The result, for example, is that a cloning operation that previously took an hour might now take just a few minutes using Virtual Volumes.
Although one of the key benefits of Virtual Volumes is the ability to use Software Policy-Based Management (SPBM), for this release of View, no default granular storage policies are created by View, as they are when you use the Virtual SAN feature. Instead, you can set a global default storage policy in vCenter Server that will apply to all Virtual Volume datastores.
Virtual Volumes has the following benefits:
Virtual Volumes supports offloading a number of operations to storage hardware. These operations include snapshotting, cloning, and Storage DRS.
With Virtual Volumes, you can use advanced storage services that include replication, encryption, deduplication, and compression on individual virtual disks.
Virtual Volumes supports such vSphere features as vMotion, Storage vMotion, snapshots, linked clones, Flash Read Cache, and DRS.
You can use Virtual Volumes with storage arrays that support vSphere APIs for Array Integration (VAAI).
Requirements and Limitations
The Virtual Volumes feature has the following limitations when used in a View deployment:
This release does not support using the View space-efficient disk format feature, which reclaims disk space by wiping and shrinking disks.
Virtual Volumes does not support using View Composer Array Integration (VAAI).
Virtual Volumes datastores are not compatible with Virtual SAN datastores for this release.
Virtual Volumes is compatible with the View Storage Accelerator feature. Virtual SAN provides a caching layer on SSD disks, and the View Storage Accelerator feature provides a content-based cache that reduces IOPS and improves performance during boot storms.
The Virtual Volumes feature has the following requirements:
vSphere 6.0 or a later release.
Appropriate hardware. Certain storage vendors are responsible for supplying storage providers that can integrate with vSphere and provide support for Virtual Volumes. Every storage provider must be certified by VMware and properly deployed.
All virtual disks that you provision on a virtual datastore must be an even multiple of 1 MB.
Virtual Volumes is a vSphere 6.0 feature. For more information about the requirements, functionality, background, and setup requirements, see the topics about Virtual Volumes in the vSphere Storage document.