Configure VMware vSAN
VMware vSAN has more capabilities that are set with every Azure VMware Solution deployment. Each cluster has their own VMware vSAN Datastore. Azure VMware Solution defaults with the following configurations per cluster:
Field | Value |
---|---|
TRIM/UNMAP | Disabled |
Space Efficiency | Deduplication and Compression |
Note
Run commands are executed one at a time in the order submitted.
In this article, learn how to:
- Enable or Disable vSAN TRIM/UNMAP
- Enable vSAN Compression Only
- Disable vSAN Deduplication and Compression
Set VMware vSAN TRIM/UNMAP
Run the Set-AVSVSANClusterUNMAPTRIM
cmdlet to enable or disable TRIM/UNMAP.
Sign in to the Azure portal.
Note
Enabling TRIM/UNMAP on your vSAN Datastore may have a negative performance impact. https://core.vmware.com/resource/vsan-space-efficiency-technologies#sec19560-sub6
Select Run command > Packages > Set-AVSVSANClusterUNMAPTRIM.
Provide the required values or change the default values, and then select Run.
Field Value Name Cluster name as defined in vCenter Server. Comma delimit to target only certain clusters. (Blank targets all clusters) Enable True or False. Retain up to Retention period of the cmdlet output. The default value is 60. Specify name for execution Alphanumeric name, for example, Disable vSAN TRIMUNMAP. Timeout The period after which a cmdlet exits if taking too long to finish. Check Notifications to see the progress.
Note
After vSAN TRIM/UNMAP is Enabled, the following lists additional requirements for it to function as intended. Once enabled, there are several prerequisites that must be met for TRIM/UNMAP to successfully reclaim no longer used capacity.
- Prerequisites - VM Level
- A minimum of virtual machine hardware version 11 for Windows
- A minimum of virtual machine hardware version 13 for Linux.
- disk.scsiUnmapAllowed flag is not set to false. The default is implied true. This setting can be used as a "stop switch" at the virtual machine level should you wish to disable this behavior on a per VM basis and do not want to use in guest configuration to disable this behavior. VMX file changes require a reboot to take effect.
- The guest operating system must be able to identify the virtual disk as thin.
- After enabling at a cluster level, the VM must be powered off and back on (a reboot is insufficient).
- Additional guidance can be found here: https://core.vmware.com/resource/vsan-space-efficiency-technologies#sec19560-sub6
Set VMware vSAN Space Efficiency
Run the Set-vSANCompressDedupe
cmdlet to set preferred space efficiency model.
Note
Changing this setting will cause a vSAN resync and performance degradation while disks are reformatted. Assure enough space is available when changing to new configuration. 25% free space or greater is recommended in general.
Sign in to the Azure portal.
Select Run command > Packages > Set-vSANCompressDedupe.
Provide the required values or change the default values, and then select Run.
Field Value Compression True or False. Deduplication True or False. (Enabling deduplication, enables both dedupe and compression) ClustersToChange Cluster name as defined in vCenter Server. Comma delimit to target multiple clusters. Retain up to Retention period of the cmdlet output. The default value is 60. Specify name for execution Alphanumeric name, for example, set cluster-1 to compress only. Timeout The period after which a cmdlet exits if taking too long to finish. Note
Setting Compression to False and Deduplication to True sets vSAN to Dedupe and Compression. Setting Compression to False and Dedupe to False, disables all space efficiency. Azure VMware Solution default is Dedupe and Compression Compression only provides slightly better performance Disabling both compression and deduplication offers the greatest performance gains, however at the cost of space utilization.
Check Notifications to see the progress.
Next steps
Now that you learned how to configure VMware vSAN, learn more about:
How to configure storage policies - Create and configure storage policies for your Azure VMware Solution virtual machines.
How to configure external identity for vCenter Server - 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.