Skip to main content
ONTAP tools for VMware vSphere 10

Create a datastore

Contributors netapp-jani

When you create a datastore at the host cluster level, ONTAP tools mounts it on all destination hosts and enables the action only if you have the required privileges.

Interoperability between native datastores with vCenter Server and ONTAP tools managed datastores

Beginning with ONTAP tools for VMware vSphere 10.4, ONTAP tools creates nested igroups for datastores, with parent igroups specific to datastores and child igroups mapped to the hosts. You can create flat igroups from ONTAP System Manager and use them to create VMFS datastores without using ONTAP tools. Refer to Manage SAN initiators and igroups for more information.

After you onboard the storage and run datastore discovery, ONTAP tools changes flat igroups in VMFS datastores to nested igroups. You cannot use earlier flat igroups to create new datastores. Use the ONTAP tools interface or REST API to reuse nested igroups.

Create a vVols datastore

Beginning with ONTAP tools for VMware vSphere 10.3, you can create a vVols datastore on ASA r2 systems with space-efficiency as thin.vVol. The VASA Provider creates a container and the desired protocol endpoints while creating the vVol datastore. The VASA Provider does not assign any backing volumes to this container.

Before you begin
  • Make sure root aggregates are not mapped to SVM.

  • Ensure that the VASA Provider is registered with the selected vCenter.

  • In the ASA r2 storage system, the SVM should be mapped to the aggregate for the SVM user.

Steps
  1. Log in to the vSphere client.

  2. Right-click on a host system, host cluster, or data center and select NetApp ONTAP tools > Create Datastore.

  3. Select vVols Datastore type.

  4. Enter the Datastore name and Protocol information.

    Note The ASA r2 system supports the iSCSI and FC protocols for vVols.
  5. Select the storage VM where you want to create the datastore.

  6. Under advanced options:

    • If you select the Custom export policy, ensure you run discovery in vCenter for all objects. It’s recommended that you don't use this option.

    • You can select Custom initiator group name for the iSCSI and FC protocols.

      Note In ASA r2 storage system type SVM, storage units (LUN/namespace) aren't created because the datastore is only a logical container.
  7. In the Storage attributes pane, you can create new volumes or use the existing volumes. However, you cannot combine these two types of volumes to create a vVols datastore.

    When creating a new volume, you can enable QoS on the datastore. By default, one volume is created for every LUN-created request. Skip this step for vVols datastores on ASA r2 storage systems.

  8. Review your selection in the Summary pane and select Finish.

Create an NFS datastore

An NFS datastore connects ESXi hosts to shared storage using the NFS protocol. They are simple and flexible and are used in VMware vSphere environments.

Steps
  1. Log in to the vSphere client.

  2. Right-click on a host system, host cluster, or data center and select NetApp ONTAP tools > Create datastore.

  3. Select NFS in the Datastore type field.

  4. Enter the datastore name, size, and protocol information in the Name and protocol pane. Select Datastore cluster and Kerberos authentication in the advanced options.

    Note Kerberos authentication is available only when the NFS 4.1 protocol is selected.
  5. Select Platform and Storage VM in the Storage pane.

  6. If you select Custom export policy under the advanced options, run the discovery in vCenter for all objects. It’s recommended that you don't use this option.

    Note You cannot create an NFS datastore using the SVM’s default or root volume policy.
    • In the advanced options, the Asymmetric toggle button is visible only if performance or capacity is selected in the platform drop-down.

    • When you choose the Any option in the platform dropdown, you can see all SVMs in the vCenter. Platform and asymmetric flag do not affect visibility.

  7. Select the aggregate for volume creation in the Storage Attributes pane. In the advanced options, choose Space Reserve and Enable QoS as required.

  8. Review the selections in the Summary pane and select Finish.

ONTAP tools creates the NFS datastore and mounts it on all hosts.

Create a VMFS datastore

VMFS is a clustered file system for storing virtual machine files. Multiple ESXi hosts can access the same VM files simultaneously for vMotion and High Availability features.

On a protected cluster:

  • You can create only VMFS datastores. Adding a VMFS datastore to a protected cluster automatically protects it.

  • You cannot create a datastore on a data center with one or more protected host clusters.

  • You cannot create a datastore on an ESXi host if the parent host cluster is protected by an "Automated Failover Duplex policy" (uniform or non-uniform configuration).

  • You can create a VMFS datastore only on an ESXi host protected by an asynchronous relationship. You cannot create and mount a datastore on an ESXi host that is part of a host cluster protected by the "Automated Failover Duplex" policy.

Before you begin

To configure an ONTAP SVM for FC protocol, refer to Configure an SVM for FC.

For more information on using NVMe/FC protocol with VMware vSphere 8.0, refer to NVMe-oF Host Configuration for ESXi 8.x with ONTAP.

For more information on using NVMe/FC with VMware vSphere 7.0, refer to ONTAP NVMe/FC Host Configuration guide and TR-4684.

Steps
  1. Log in to the vSphere client.

  2. Right-click on a host system, host cluster, or data center and select NetApp ONTAP tools > Create Datastore.

  3. Select VMFS datastore type.

  4. Enter the datastore name, size, and protocol information in the Name and Protocol pane. To add the new datastore to an existing VMFS cluster, select the datastore cluster in Advanced Options.

  5. Select storage VM in the Storage pane. Provide the Custom initiator group name in the Advanced options section as required. You can choose an existing igroup for the datastore or create a new igroup with a custom name.

    When NVMe/FC or NVMe/TCP protocol is selected, a new namespace subsystem is created and is used for namespace mapping. ONTAP tools creates the namespace subsystem using the auto-generated name that includes the datastore name. You can rename the namespace subsystem in the custom namespace subsystem name field in the advanced options of the Storage pane.

  6. From the storage attributes pane:

    1. Select Aggregate from the drop-down options.

      Note For ASA r2 storage systems, the Aggregate option is not shown because storage is disaggregated. When you choose an ASA r2 storage system type SVM, the storage attributes page shows the options for enabling QoS.
    2. ONTAP tools creates a storage unit (LUN/Namespace) with a thin space reserve based on the selected protocol.

      Note Beginning in ONTAP 9.16.1, ASA r2 storage systems support up to 12 nodes per cluster.
    3. Select the Performance service level for ASA r2 storage systems with 12 nodes SVM that is a heterogeneous cluster. This option is unavailable if the selected SVM is a homogeneous cluster or uses an SVM user.

      'Any' is the default performance service level (PSL) value. This setting creates the storage unit using the ONTAP balanced placement algorithm. However, you can select the performance or extreme option as required.

    4. Select Use existing volume, Enable QoS options as required, and provide the details.

      Note In the ASA r2 storage type, volume creation or selection doesn't apply to storage unit creation(LUN/Namespace). Therefore, these options aren't shown.
      Note You cannot use the existing volume to create a VMFS datastore with NVMe/FC or NVMe/TCP protocol. Create a new volume for the VMFS datastore.
  7. Review the datastore details in the Summary pane and select Finish.

Note If you create the datastore on a protected cluster, you can see a read-only message: "The datastore is being mounted on a protected Cluster."
Result

ONTAP tools creates the VMFS datastore and mounts it on all the hosts.