Configuring virtual volume datastores

You can use VASA Provider for ONTAP to create and manage virtual volumes (VVols). You can provision, edit, mount, and delete a virtual datastore. You can also add storage to the datastore or remove storage from the virtual datastore. VVols provide greater flexibility. You can provision and manage every virtual machine and the related VMDK.

A VVol datastore consists of one or more FlexVol volumes within a storage container (also called "backing storage"). A virtual machine can be spread across one datastore or multiple datastores.

While you can create a VVol datastore that has multiple FlexVol volumes, all of the FlexVol volumes within the storage container must use the same protocol (NFS, iSCSI, or FCP) and the same storage virtual machines (SVMs).

You do not require detailed knowledge of the underlying storage. For example, you do not have to identify a specific FlexVol volume to contain the storage. After you add FlexVol volumes to the VVol datastore, the storage container manages the storage requirements and prevents any situations where one FlexVol volume is full while another FlexVol volume has no storage.

Note: It is a good practice to include multiple FlexVol volumes in a VVol datastore for performance and flexibility. Because FlexVol volumes have LUN count restrictions that limit the number of virtual machines, including multiple FlexVol volumes allows you to store more virtual machines in your VVol datastore.

As part of the setup process, you must specify a storage capability profile for the VVol datastore that you are creating. You can select one or more VASA Provider storage capability profiles for a VVol datastore. You can also specify a default storage capability profile for any VVol datastores that are automatically created in that storage container.

VASA Provider creates different types of VVols during virtual machine provisioning or VMDK creation, as required.