Today, with VMware Virtual Volumes (VVols), the vSphere administrator takes greater responsibility for provisioning storage and becomes responsible for defining the various storage policies for VMs. In addition, Storage Administrators no longer have the arduous task of managing storage to VM mapping or create one datastore per VM. VVols facilities pre-determined policy-driven automation, which enables more agile storage consumption for VMs. This ultimately delivers faster provisioning for new applications and any associated data services. Moreover, storage administrators can create a snapshot of a specific VM. This also holds true for remote replication, CDP, and other virtual disk-specific functions.
VMware Virtual Volumes
VVols enable policy-based self-provisioning and management of storage at the time virtual machines and storage are created. First, the storage administrator creates a “storage container” that is assigned for usage by vSphere. This eliminates the need to assign individual volumes every time a vSphere administrator requests it. Then, the vSphere administrator assigns policies based on the characteristics needed to provision a VM. For example, the policies could be gold, silver or bronze - gold being high performance and high availability; silver being medium performance, medium availability, and bronze for low performance, low availability. After that, VMs can be created in the container from the available space – using the storage profiles. Finally, vSphere Storage (VASA) API connects the new VM to the storage container. In short, when deployed, VVols take away the storage management burden that comes from provisioning VMs..