Create a Datastore (AVS Storage Container)

Everpure Cloud Azure Native

Audience
Public
Source Type
Documentation

To begin using Everpure Cloud as an external storage provider for your Azure VMware Solution (AVS) software-defined data center (SDDC), you must first create a VMware Datastore (seen as an AVS Storage Container in Azure Portal).

Each Storage Pool can be connected to one AVS resource and can have one or more Datastores (AVS Storage Containers). You can also have multiple Storage Pools which are connected to one particular AVS instance or several different AVS instances.

Create a Datastore in vSphere Client

  1. Ensure that a Storage Pool has been created and is already connected to your AVS SDDC following this KB. The datastore relies on this connection to provision and manage storage for your AVS workloads.
  2. In your browser, log into the vSphere Client using your preferred connection method.

  3. Go to the tab Inventories and click on Hosts and Clusters.

  4. In the menu find the Cluster object (typically named "Cluster-1"), then right-click it to open the context menu.

  5. Find the Everpure section in the context menu and click on Create Datastore.

  6. Enter a name for your new VMFS datastore and specify provisioned size.

    Note: Please note that the specified size of a datastore (container) is virtual only and does not reflect the real size of underlying resources. Provisioned size can be changed later using Resize Datastore workflow here.
  7. For Storage section, select the Storage Pool resource and click Next.

    Note:

    The name of your datastore will then match the name of a Storage Container resource visible in the Storage Pool detail in Azure portal.

  8. Optionally specify the datastore QoS limits for Bandwidth and IOPS.

  9. Confirm the workflow by clicking o the Finish button. From now on, you can use this VMFS datastore as a external storage for a new VMs hosted on the SDDC.

Note: Please note that during Datastore creation workflow, it can happen that an error message about Datastore mounting or connecting failed on subset of the hosts in the cluster. This is expected behavior especially in situations when the host is replaced, added or removed. There is built-in mechanism that should mount/connect the Datastore on all available hosts in the cluster automatically as soon as possible when host is ready.