|
| 1 | +--- |
| 2 | +# Required metadata |
| 3 | +# For more information, see https://learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata |
| 4 | +# For valid values of ms.service, ms.prod, and ms.topic, see https://learn.microsoft.com/en-us/help/platform/metadata-taxonomies |
| 5 | + |
| 6 | +title: Configure VMware vSAN ESA |
| 7 | +description: Configure VMware vSAN ESA |
| 8 | +author: jkpravinkumar # GitHub alias |
| 9 | +ms.author: pjeyakumar # Microsoft alias |
| 10 | +ms.service: azure-vmware |
| 11 | +ms.topic: how-to |
| 12 | +ms.date: 05/12/2025 |
| 13 | +--- |
| 14 | + |
| 15 | +# Configure VMware vSAN ESA |
| 16 | + |
| 17 | +VMware [vSAN](https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/8-0/release-notes/vmware-vsan-803-release-notes.html) ESA (Express Storage Architecture) offers enhanced capabilities that are configured by default with each Azure VMware Solution deployment. Each cluster uses its own high-performance vSAN ESA datastore. The following table shows the Azure VMware Solution host types that support vSAN ESA as the default architecture type, along with the configurations per cluster: |
| 18 | + |
| 19 | +| **Field** | **Value** | |
| 20 | +| --- | --- | |
| 21 | +| **TRIM/UNMAP** | Enabled by default.| |
| 22 | +| **Space Efficiency** | Compression only (Storage policy managed compression). Deduplication isn't supported.| |
| 23 | + |
| 24 | +> [!NOTE] |
| 25 | +> Run commands are executed one at a time in the order submitted. |
| 26 | +
|
| 27 | +In this article, you learn more about: |
| 28 | + |
| 29 | +> [!div class="checklist"] |
| 30 | +> - Supported host type |
| 31 | +> - Supported vSAN services |
| 32 | +> - How to enable or disable vSAN TRIM/UNMAP |
| 33 | +> - How to enable vSAN Compression |
| 34 | +> - How to enable or disable vSAN Data-In-Transit Encryption |
| 35 | +
|
| 36 | +## Supported host type |
| 37 | +vSAN ESA (Express Storage Architecture) is supported on the following Azure VMware Solution host types: |
| 38 | + |
| 39 | +- AV48 |
| 40 | + |
| 41 | +## Supported vSAN services |
| 42 | + |
| 43 | +The following table shows the list of vSAN features available in Azure VMware Solution. |
| 44 | + |
| 45 | + | **vSAN Services** | **Availability** | |
| 46 | + | --- | --- | |
| 47 | + | **Auto-Policy Management** | Not supported| |
| 48 | + | **Compression** | Supported| |
| 49 | + | **Data-at-rest encryption** | Supported, enabled by default| |
| 50 | + | **Data-in-transit encryption** | Supported| |
| 51 | + | **Deduplication** | Not supported| |
| 52 | + | **File Service** | Not supported| |
| 53 | + | **Guest Trim/Unmap** | Supported, enabled by default| |
| 54 | + | **iSCSI Target Service** | Not supported| |
| 55 | + | **Support for Windows Server Failover Clusters (WSFC)** | Supported| |
| 56 | + | **vSAN Data Protection** | Not supported| |
| 57 | + | **vSAN Performance Service** | Supported| |
| 58 | + | **vSAN Stretched cluster** | Supported| |
| 59 | + | **vSAN Support Insight** | Not supported| |
| 60 | + |
| 61 | +## Set VMware vSAN TRIM/UNMAP |
| 62 | + |
| 63 | +Guest Trim/Unmap is enabled by default and can't be disabled for cluster with vSAN ESA. Run command `Set-AVSVSANClusterUNMAPTRIM` isn't applicable for vSAN ESA based clusters. |
| 64 | + |
| 65 | +> [!NOTE] |
| 66 | +> vSAN TRIM/UNMAP is enabled by default on vSAN ESA based clusters. To disable UNMAP at the VM level, the following lists additional requirements are needed for it to function as intended. |
| 67 | +>- All VMs in vSAN ESA clusters are set by default to use UNMAP inherited from the cluster level. UNMAP can be disabled using the disk.scsiUnmapAllowed flag with a value of 'false' at the virtual machine level, should you wish to disable this behavior on a per-VM basis. VMX file changes require a reboot to take effect. |
| 68 | +>- The guest operating system must be able to identify the virtual disk as thin. |
| 69 | +
|
| 70 | +## Set VMware vSAN space efficiency |
| 71 | + |
| 72 | +In vSAN ESA (Express Storage Architecture), space efficiency is enabled through Storage policy managed compression. See [VMware documentation](https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/8-0/vsan-administration/increasing-space-efficiency-in-a-vsan-cluster/using-deduplication-and-compression-in-vsan-cluster.html). |
| 73 | + |
| 74 | +## Set VMware vSAN Data-In-Transit Encryption |
| 75 | + |
| 76 | +Run the `Set-vSANDataInTransitEncryption` cmdlet to enable or disable data-in-transit encryption for all clusters or specified clusters of an SDDC. |
| 77 | + |
| 78 | +> [!NOTE] |
| 79 | +> Changing this setting impacts performance. See [VMware KB](https://blogs.vmware.com/virtualblocks/2021/08/12/storageminute-vsan-data-encryption-performance/). |
| 80 | +
|
| 81 | +1. Sign in to the [Azure portal](https://portal.azure.com/). |
| 82 | + |
| 83 | +1. Select **Run command** > **Packages** > **Set-vSANDataInTransitEncryption**. |
| 84 | + |
| 85 | +1. Provide the required values or change the default values, and then select Run. |
| 86 | + |
| 87 | + | **Field** | **Value** | |
| 88 | + | --- | --- | |
| 89 | + | **Cluster Name** | Name of the cluster. Leave blank if necessary to enable for whole SDDC else enter comma separated list of names. | |
| 90 | + | **Enable**| Specify True/False to Enable/Disable the feature.| |
| 91 | + |
| 92 | +1. Check Notifications to see the progress. |
| 93 | + |
| 94 | +>[!NOTE] |
| 95 | +>You can also use the `Get-vSANDataInTransitEncryptionStatus` command to check for the current status or status after performing the `Set-vSANDataInTransitEncryptionStatus` operation and verify the cluster's current encryption state. |
| 96 | +
|
| 97 | +## Next steps |
| 98 | + |
| 99 | +Now that you learned how to configure VMware vSAN, learn more about: |
| 100 | + |
| 101 | +- [How to configure storage policies](/azure/azure-vmware/configure-storage-policy) - Create and configure storage policies for your Azure VMware Solution virtual machines. |
| 102 | + |
| 103 | +- [How to configure external identity for vCenter Server](/azure/azure-vmware/configure-identity-source-vcenter) - vCenter Server has a built-in local user called cloudadmin and assigned to the CloudAdmin role. The local cloudadmin user is used to set up users in Active Directory (AD). With the Run command feature, you can configure Active Directory over LDAP or LDAPS for vCenter Server as an external identity source. |
| 104 | + |
0 commit comments