Table of ContentsView in Frames

Working with VVOLs

You can use VASA Provider for clustered Data ONTAP to create and manage VMware virtual volumes (VVOLs). You can provision a VVOL datastore, edit it, add and remove storage, mount it, and delete it.

A VVOL datastore consists of one or more FlexVols within a storage container (also called “backing storage”). A VVOL can contain multiple datastores.

While you can create a VVOL datastore that has multiple FlexVols, all the FlexVols within the storage container must use the same protocol (NFS, iSCSI, or FCP) and the same Storage Virtual Machine (SVM, formerly known as Vserver).

The Provision VVOL Datastore wizard provided by VASA Provider automatically sets up the VVOL datastore. You do not need a detailed knowledge of the underlying storage. For example, you do not need to identify a specific FlexVol to hold the storage. After you add FlexVols to the VVOL datastore, the storage container manages the storage needs and prevents any situations where one FlexVol is full while another has no storage.

Note: It is a good practice to include multiple FlexVols in a VVOL datastore. Because FlexVols have LUN count restrictions that limit the number of virtual machines, having multiple FlexVols can increase performance.

As part of the setup, the wizard prompts you to specify a storage capability profile for the VVOL datastore you are creating. You can apply both VASA Provider storage capability profiles and VMware VM Storage Policies to a VVOL datastore. The profiles specify the FlexVol attributes. Using them enables you to do policy-based management within a datastore instead of just using policy-based management as a datastore selector.

The wizard also prompts you to specify a default storage capability profile for any VVOL datastores that are automatically created in that storage container. As needed, VASA Provider automatically creates the following types of VVOL datastores: