Skip to main content
VCP

Manage datastores

Contributors netapp-pcarriga netapp-dbagwell amgrissino
PDFs

Using the NetApp Element Plug-in for VMware vCenter Server, you can manage datastores that are backed by Element volumes. You can create, extend, clone, share, or delete datastores. You can also use VAAI UNMAP to allow a cluster to reclaim freed block space from thinly provisioned VMFS datastores.

What you'll need
Options
Tip Monitor datastore operations for completion using task monitoring in vSphere.

Create a datastore

You can create a datastore from the plug-in extension.

What you'll need
Steps

  1. In your vSphere Web Client, open the Management tab:

    • Beginning with Element vCenter plug-in 5.0, select NetApp Element Remote Plugin > Management > Management.

    • For Element vCenter plug-in 4.10 and earlier, select NetApp Element Management > Management.

    Note If two or more clusters are added, ensure that the cluster you intend to use for the task is selected in the navigation bar.

  2. From the Datastore page, select Create Datastore.

  3. Enter a name for the datastore.

    Tip Use a unique name for each datastore in a data center. For multiple cluster or vCenter Server environments, use descriptive naming best practices.

  4. Select Next.

  5. Select one or more required hosts for the datastore.

    Note You need at least one connected host before you can create a new datastore. If your host has multiple initiators, select an initiator or the host to select all initiators. If you are using vCenter Linked Mode, only hosts available to the vCenter Server to which the cluster is assigned are available to select.

  6. Select Next.

  7. In the Configure Volume pane, select an existing volume or create a new volume for the new datastore:

    Select existing volume

    If you select an existing volume, you must meet the following prerequisites:

    • To use a volume access group:

      1. Create a new volume with 512e enabled.

      2. Add the volume to an access group that contains the one or more target host initiators.

    • To use CHAP:

      1. Ensure CHAP is configured for each target host iSCSI adapter.

      2. Create a new volume with 512e enabled using one of the following options:

        • Use an account with the appropriate CHAP settings for each target host.

        • Create an account and configure the target and initiator secrets.

      3. View the volume details.

      4. Add the volume IQN to each target host iSCSI adapter static discovery table.

    Create new volume

    1. Enter a name for the volume that backs the datastore.

    2. Select a user account from the account list.

    3. Enter the total size of the volume you want to create.

      Note The default volume size selection is in GB. You can create volumes using sizes measured in GB or GiB:
      1GB = 1 000 000 000 bytes
      1GiB = 1 073 741 824 bytes

      By default, 512 byte emulation is set to ON for all the new volumes.

    4. In the Quality of Service area, do one of the following:

      1. Under Policy, select an existing QoS policy.

      2. Under Custom Settings, set customized minimum, maximum, and burst values for IOPS or use the default QoS values.

        Tip QoS policies are best for service environments, for example, with database, application, or infrastructure servers that rarely reboot and need constant equal access to storage. Custom QoSSIOC automation is best for light use VMs, such as virtual desktops or specialized kiosk-type VMs, that may be rebooted, powered on, or powered off daily or several times a day. QoSSIOC automation and QoS policies should not be used together.
        Tip Volumes that have a Max or Burst IOPS value greater than 20,000 IOPS might require high queue depth or multiple sessions to achieve this level of IOPS on a single volume.

  8. Select Next.

  9. Configure the authorization type for host access by choosing one of the following:

    • Use Volume Access Group: Select to explicitly limit which initiators can see volumes.

    • Use CHAP: Select for secure secret-based access with no limits on initiators.

  10. Select Next.

  11. If you selected Use Volume Access Group, configure the volume access groups for the selected hosts.

    The volume access groups listed in Required by Selected Initiators are already associated with one or more of the host initiators you selected in an earlier step

    1. Select additional volume access groups or create new ones to associate with available initiators:

      • Available: Other volume access group options in the cluster.

      • Create New Access Group: Enter the name of the new access group and select Add.

    2. Select Next.

    3. In the Configure Hosts' Access pane, associate available host initiators (IQN or WWPN) with the volume access groups you selected in the previous pane. If a host initiator is already associated with a volume access group, the field is read-only for that initiator. If a host initiator does not have a volume access group association, select an option from the list next to the initiator.

    4. Select Next.

  12. If you want to enable QoSSIOC automation, check Enable QoS & SIOC and then configure the QoSSIOC settings.

    Tip If you are using QoS policies, do not enable QoSSIOC. QoSSIOC will override and adjust QoS values for volume QoS settings.

    If the QoSSIOC service is not available, you must first configure QoSSIOC settings:

    1. Select Enable QoS & SIOC.

    2. Configure the Burst Factor.

      Note The burst factor is a multiple of the IOPS limit (SIOC) setting for the VMDK. If you change the default, make sure to use a burst factor value that will not exceed the maximum burst limit for an Element volume when the burst factor value is multiplied by the IOPS limit for any VMDK.

    3. (Optional) Select Override Default QoS and configure the settings.

      Note If the Override Default QoS setting is disabled for the datastore, the Shares and Limit IOPS values are automatically set based on the default SIOC settings of each VM.
      Tip Do not customize the SIOC share limit without also customizing the SIOC IOPS limit.
      Tip By default, the maximum SIOC disk shares are set to Unlimited. In a large VM environment such as VDI, this can lead to overcommitting maximum IOPS on the cluster. When you enable QoSSIOC, always check the Override Default QoS and set the Limit IOPS option to something reasonable.

  13. Select Next.

  14. Confirm the selections and click Finish.

  15. To view the progress of the task, use Task Monitoring in vSphere. If the datastore does not appear in the list, refresh the view.

View the datastore list

You can view available datastores on the Datastores page from plug-in extension point.

  1. In your vSphere Web Client, open the Management tab:

    • Beginning with Element vCenter plug-in 5.0, select NetApp Element Remote Plugin > Management > Management.

    • For Element vCenter plug-in 4.10 and earlier, select NetApp Element Management > Management.

    Note If two or more clusters are added, select the cluster you want to use in the navigation bar.

  2. Review the list of datastores.

    Note Datastores spanning multiple volumes (mixed datastores) are not listed. Datastore views show only datastores that are available on ESXi hosts from the selected NetApp Element cluster.

  3. Review the following information:

    • Name: The name assigned to the datastore.

    • Host Name(s): The address of each associated host device.

    • Status: The possible values Accessible or Inaccessible indicate whether or not the datastore is currently connected to vSphere.

    • Type: The VMware file system datastore type.

    • Volume Name: The name assigned to the associated volume.

    • Volume NAA: Globally unique SCSI device identifier for the associated volume in NAA IEEE Registered Extended format.

    • Total Capacity (GB): Total formatted capacity of the datastore.

    • Free Capacity (GB): Space that is available for the datastore.

    • QoSSIOC Automation: Indicates whether or not QoSSIOC automation is enabled. Possible values:

      • Enabled: QoSSIOC is enabled.

      • Disabled: QoSSIOC is not enabled.

      • Max Exceeded: Volume Max QoS has exceeded the limit value specified.

Extend a datastore

You can extend a datastore to increase volume size using the plug-in extension point. Extending the datastore also extends the VMFS volume related to that datastore.

Steps

  1. In your vSphere Web Client, open the Management tab:

    • Beginning with Element vCenter plug-in 5.0, select NetApp Element Remote Plugin > Management > Management.

    • For Element vCenter plug-in 4.10 and earlier, select NetApp Element Management > Management.

    Note If two or more clusters are added, select the cluster you want to use in the navigation bar.

  2. From the Datastores page, select the check box for the datastore you want to extend.

  3. Select Actions.

  4. In the resulting menu, select Extend.

  5. In the New Datastore Size field, enter the required size for the new datastore and select GB or GiB.

    Note Extending the datastore will consume the entire volume's size. The new datastore size cannot exceed the unprovisioned space available on the selected cluster or the maximum volume size the cluster allows.

  6. Select OK.

  7. Refresh the page.

Clone a datastore

You can clone datastores using the plug-in, which includes mounting the new datastore to the desired ESXi server or cluster. You can name the datastore clone and configure its QoSSIOC, volume, host, and authorization type settings.

If virtual machines exist on the source datastore, virtual machines on the clone datastore will be brought into the inventory with new names.

Volume size for the clone datastore matches the size of the volume backing the source datastore. By default, 512 byte emulation is set to ON for all the new volumes.

What you'll need

  • At least one host must be connected to vCenter Server.

  • At least one cluster must be added and running.

    Note If you are using vCenter Linked Mode, be sure that you have added your cluster with the correct vCenter Server.

  • Available unprovisioned space must be equal to or more than the source volume size.

  • At least one user account must be created.

Steps

  1. In your vSphere Web Client, open the Management tab:

    • Beginning with Element vCenter plug-in 5.0, select NetApp Element Remote Plugin > Management > Management.

    • For Element vCenter plug-in 4.10 and earlier, select NetApp Element Management > Management.

    Note If two or more clusters are added, select the cluster you want to use in the navigation bar.

  2. From the Datastores page, select the check box for the datastore you want to clone.

  3. Select Actions.

  4. In the resulting menu, select Clone.

    Note If you attempt to clone a datastore that contains virtual machines with attached disks not located on the selected datastore, copies of the virtual machines on the cloned datastore will not be added to the virtual machine inventory.

  5. Enter a datastore name.

    Tip Use a unique name for each datastore in a data center. For multiple cluster or vCenter Server environments, use descriptive naming best practices.

  6. Select Next.

  7. Select one or more required hosts for the datastore.

    Note You need at least one connected host before you can create a new datastore. If your host has multiple initiators, select an initiator or the host to select all initiators. If you are using vCenter Linked Mode, only hosts available to the vCenter Server to which the cluster is assigned are available to select.

  8. Select Next.

  9. In the Configure Volume pane, do the following:

    1. Enter a name for the new NetApp Element volume that backs the clone datastore.

    2. Select a user account from the account list.

      Note You need at least one existing user account before you can create a volume.

    3. In the Quality of Service area, do one of the following:

      • Under Policy, select an existing QoS policy, if available.

      • Under Custom Settings, set customized minimum, maximum, and burst values for IOPS or use the default QoS values.

        Tip QoS policies are best for service environments, for example, with database, application, or infrastructure servers that rarely reboot and need constant equal access to storage. Custom QoSSIOC automation is best for light use VMs, such as virtual desktops or specialized kiosk-type VMs, that may be rebooted, powered on, or powered off daily or several times a day. QoSSIOC automation and QoS policies should not be used together.
        Tip Volumes that have a Max or Burst IOPS value greater than 20,000 IOPS might require high queue depth or multiple sessions to achieve this level of IOPS on a single volume.

  10. Select Next.

  11. Configure authorization type for host access by selecting one of the following options:

    • Use Volume Access Group: Select to explicitly limit which initiators can see volumes.

    • Use CHAP: Select for secure secret-based access with no limits on initiators.

  12. Select Next.

  13. If you selected Use Volume Access Group, configure the volume access groups for the selected hosts.

    The volume access groups listed in Required by Selected Initiators are already associated with one or more of the host initiators you selected in an earlier step.

    1. Select additional volume access groups or create new ones to associate with available initiators:

      • Available: Other volume access group options in the cluster.

      • Create New Access Group: Enter the name of the new access group and click Add.

    2. Select Next.

    3. In the Configure Hosts' Access pane, associate available host initiators (IQN or WWPN) with the volume access groups you selected in the previous pane.

      If a host initiator is already associated with a volume access group, the field is read-only for that initiator. If a host initiator does not have a volume access group association, select an option from the drop-down list next to the initiator.

    4. Select Next.

  14. If you want to enable QoSSIOC automation, check the Enable QoS & SIOC box and then configure the QoSSIOC settings.

    Important If you are using QoS policies, do not enable QoSSIOC. QoSSIOC will override and adjust QoS values for volume QoS settings.

    If the QoSSIOC service is not available, you must first configure settings on the QoSSIOC Settings page from the plug-in extension point:

    1. Select Enable QoS & SIOC.

    2. Configure the Burst Factor.

      Note The burst factor is a multiple of the IOPS limit (SIOC) setting for the VMDK. If you change the default, make sure to use a burst factor value that will not exceed the maximum burst limit for a NetApp Element volume when the burst factor value is multiplied by the IOPS limit for any VMDK.

    3. Optional: Select Override Default QoS and configure the settings.

      If the Override Default QoS setting is disabled for the datastore, the Shares and Limit IOPS values are automatically set based on the default SIOC settings of each VM.

      Tip Do not customize the SIOC share limit without also customizing the SIOC IOPS limit.
      Tip By default, the maximum SIOC disk shares are set to Unlimited. In a large VM environment such as VDI, this can lead to overcommitting maximum IOPS on the cluster. When you enable QoSSIOC, always check the Override Default QoS and set the Limit IOPS option to something reasonable.

  15. Select Next.

  16. Confirm the selections and select Finish.

  17. Refresh the page.

Share a datastore

You can share a datastore with one or more hosts using the plug-in extension point.

Datastores can be shared only among hosts within the same data center.

What you'll need

  • At least one cluster must be added and running.

    Note If you are using vCenter Linked Mode, be sure that you have added your cluster with the correct vCenter Server.

  • There must be more than one host under the selected data center.

Steps

  1. In your vSphere Web Client, open the Management tab:

    • Beginning with Element vCenter plug-in 5.0, select NetApp Element Remote Plugin > Management > Management.

    • For Element vCenter plug-in 4.10 and earlier, select NetApp Element Management > Management.

    Note If two or more clusters are added, select the cluster you want to use in the navigation bar.

  2. From the Datastores page, select the check box for the datastore you want to share.

  3. Select Actions.

  4. In the resulting menu, select Share.

  5. Configure authorization type for host access by selecting one of the following options:

    • Use Volume Access Group: Select this option to explicitly limit which initiators can see volumes.

    • Use CHAP: Select this option for secure secret-based access with no limits on initiators.

  6. Select Next.

  7. Select one or more required hosts for the datastore.

    Note You need at least one connected host before you can create a new datastore. If your host has multiple initiators, select an initiator or all initiators by selecting the host. If you are using vCenter Linked Mode, only hosts available to the vCenter Server to which the cluster is assigned are available to select.

  8. Select Next.

  9. If you selected Use Volume Access Group, configure the volume access groups for the selected hosts.

    The volume access groups listed in Required by Selected Initiators are already associated with one or more of the host initiators you selected in an earlier step.

    1. Select additional volume access groups or create new ones to associate with available initiators:

      • Available: Other volume access group options in the cluster.

      • Create New Access Group: Enter the name of the new access group and click Add.

    2. Select Next.

    3. In the Configure Hosts' Access pane, associate available host initiators (IQN or WWPN) with the volume access groups you selected in the previous pane.

      If a host initiator is already associated with a volume access group, the field is read-only for that initiator. If a host initiator does not have a volume access group association, select an option from the drop-down list next to the initiator.

  10. Confirm the selections and select Finish.

  11. Refresh the page.

Perform VAAI UNMAP

If you want a cluster to reclaim freed block space from thinly provisioned VMFS5 datastores, use the VAAI UNMAP feature.

What you'll need

  • Ensure that the datastore you are using for the task is VMFS5 or earlier. VAAI UNMAP is unavailable for VMFS6 because ESXi performs the task automatically

  • Ensure that the ESXi host system settings are enabled for VAAI UNMAP:

    esxcli system settings advanced list -o/VMFS3/EnableBlockDelete

    The integer value must be set to 1 to enable.

  • If the ESXi host system settings are not enabled for VAAI UNMAP, set the integer value to 1 with this command:

    esxcli system settings advanced set -i 1 -o /VMFS3/EnableBlockDelete

Steps

  1. In your vSphere Web Client, open the Management tab:

    • Beginning with Element vCenter plug-in 5.0, select NetApp Element Remote Plugin > Management > Management.

    • For Element vCenter plug-in 4.10 and earlier, select NetApp Element Management > Management.

    Note If two or more clusters are added, select the cluster you want to use in the navigation bar.

  2. From the Datastores page, select the check box for the datastore on which you want to use VAAI UNMAP..

  3. In the resulting menu, select Actions.

  4. Select VAAI Unmap.

  5. Select a host by name or IP address.

  6. Enter the host user name and password.

  7. Confirm the selections and select OK.

Delete a datastore

You can delete a datastore using the plug-in extension point. This operation permanently deletes all the files associated with the VMs on the datastore that you want to delete. The plug-in does not delete datastores that contain registered VMs.

  1. In your vSphere Web Client, open the Management tab:

    • Beginning with Element vCenter plug-in 5.0, select NetApp Element Remote Plugin > Management > Management.

    • For Element vCenter plug-in 4.10 and earlier, select NetApp Element Management > Management.

    Note If two or more clusters are added, select the cluster you want to use in the navigation bar.

  2. From the Datastores page, select the check box for the datastore you want to delete.

  3. Select Actions.

  4. In the resulting menu, select Delete.

  5. (Optional) If you want to delete the NetApp Element volume that is associated with the datastore, select the Delete associated volume check box.

    Note You can also choose to retain the volume and later associate it with another datastore.

  6. Select Yes.

Find more information