Do you enable or disable IO Metrics for Storage DRS

May 20, 2021

Enable or Disble IO Metrics in Storage DRS

The question has come up a few times regarding whether to enable or disable IO Metrics when using Storage DRS.  The answer is; It depends on the usage and setup of the environment.

One array, multiple datastores

For example, if you have a single array providing multiple volumes or LUNs for multiple datastores in a datastore cluster, then you want to have IO Metrics enabled. The reason being, the analysis done by my SDRS using IO Metrics will determine the datastores are on the same array by seeing the same IO from different datastores. Subsequently, it won't move a VM from one datastore to another if it sees IO contention becasue it will not result in any change in performance. This is because the datastores are all on the same array. In this case, SDRS and SIOC will look mostly at capacity and make adjustments accordingly.

vSphere Metro Storage Cluster (vMSC)

If you are using vMSC, the recommendation is to disable IO Metrics. See vSphere Storage DRS or vSphere Storage I/O Control support in a vSphere Metro Storage Cluster environment (2042596) 

Array-based Auto-tiering

Another possible scenario is with array-based auto-tiering. Some arrays have a function to move data around between different tiers on the array based on how active or "hot"  the data is. In some cases SIOC or IO metrics and array-based auto-tiering can conflict. To avoid this, if possible you will want to install the array vendor's VASA (vSphere Storage APIs for Storage Awareness) provider. The VASA allows Storage DRS to understands storage array advanced features such as deduplication, auto-tiering, snapshotting, replication, thin-provisioning. By using VASA, the array will report whether it is using auto-tiering and vSphere will not use the IO metrics and allow the array to manage data placement on the array itself.

For those arrays that have auto-tiering and do not have a VASA provider, VMware recommends you disable "IO balance automation level"  SDRS does not conflict with the auto-tiering process and migrate VMs needlessy.

image 77


Storage DRS Resources






Filter Tags

Storage ESXi Distributed Resource Scheduler (DRS) Blog Best Practice Fundamental Intermediate Optimize

Jason Massae

Read More from the Author

Jason is the vVols and Core Storage Technical Marketing Architect for the HCIBU at VMware. Before joining VMware, he came from one of the largest flash and memory manufacturers in the world. There he architected and lead global teams in virtualization strategies for IT. Working with the storage business unit, he helped test and validate SSDs for VMware vSAN. Now his primary focus is vSphere vVols and Core Storage.