Skip to main content

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).

The Provision VVol Datastore wizard that is provided by VASA Provider automatically sets up the VVol datastore. 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. Because FlexVol volumes have LUN count restrictions that limit the number of virtual machines, including multiple FlexVol volumes can increase performance.

As part of the setup process, the wizard prompts you to specify a storage capability profile for the VVol datastore that you are creating. You must select one or more VASA Provider storage capability profiles for a VVol datastore.

The wizard also prompts you to 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.

  • Config:

    VMware vSphere uses this VVol datastore to store configuration information.

    In SAN (block) implementations, the storage is a 4 GB LUN.

    In an NFS implementation, this is a directory containing VM config files such as the vmx file and pointers to other VVol datastores.

  • Data:

    This VVol contains operating system information and user files.

    In SAN implementations, this is a LUN that is the size of the virtual disk.

    In an NFS implementation, this is a file that is the size of the virtual disk.

  • Swap:

    This VVol is created when the virtual machine is powered on and is deleted when the virtual machine is powered off.

    In SAN implementations, this is a LUN that is the size of the virtual memory.

    In an NFS implementation, this is a file that is the size of the virtual memory.

  • Memory:

    This VVol is created if the memory snapshots option is selected when creating VM snapshot.

    In SAN implementations, this is a LUN that is the size of the virtual memory.

    In an NFS implementation, this is a file that is the size of the virtual memory.

  1. Considerations for creating and editing storage capability profiles
    You should be aware of the considerations for creating and editing storage capability profiles.
  2. Creating and editing storage capability profiles
    You have several options for using VASA Provider for ONTAP to create new storage capability profiles. You can create a profile manually, you can automatically generate a profile based on the capabilities of a datastore, or you can modify the profile to meet your requirements. After setting up a profile, you can edit the profile as required.
  3. Mapping datastores to storage capability profiles
    You can map the datastores that are associated with VASA Provider for ONTAP to storage capability profiles. You can assign a profile to a datastore that is not associated with a storage capability profile. You can also change the storage capability profile that is associated with a datastore.
  4. Provisioning VVol datastores
    You can use VASA Provider for ONTAP to create virtual volume (VVol) datastores. The Provision VVol Datastore wizard performs all of the necessary storage-side setup processes such as creating export policies, creating initiator groups, and mapping LUNs.
  5. Adding storage to a VVol datastore
    You can increase the available storage by using the Add Storage wizard to add FlexVol volumes to an existing virtual volume (VVol) datastore.
  6. Enabling VM Storage Policies
    When you use virtual volumes (VVols), you have the option of using VM Storage Policies and storage capability profiles. Before you can set up any VM Storage Policies, you must enable them for each host and cluster that is associated with the VVols.
  7. Mounting a VVol datastore
    You can mount a virtual volume (VVol) datastore to one or more additional hosts by using the Mount VVol Datastore dialog box.
  8. Setting alarm thresholds in VASA Provider for ONTAP
    VASA Provider for ONTAP enables you to set alarms to notify you when volume thresholds and aggregate thresholds reach certain limits.