The Virtual Volumes functionality offers several benefits and advantages. When you work with Virtual Volumes, you must follow specific guidelines.
Virtual Volumes has the following characteristics:
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.
With Virtual Volumes, storage vendors can use native snapshot facilities to improve performance of vSphere snapshots.
You can use Virtual Volumes with storage arrays that support vSphere APIs for Array Integration (VAAI).
Virtual Volumes supports backup software that uses vSphere APIs for Data Protection (VADP).
Virtual Volumes Guidelines and Limitations
Follow these guidelines when you use Virtual Volumes.
Because the Virtual Volumes environment requires vCenter Server, you cannot use Virtual Volumes with a standalone host.
Virtual Volumes does not support RDMs.
A Virtual Volumes storage container cannot span across different physical arrays.
Host profiles that contain virtual datastores are vCenter Server specific. After you extract this type of host profile, you can attach it only to hosts and clusters managed by the same vCenter Server as the reference host.