Hi all,
Suppose in a VSAN Stretched Cluster:
- A VMDK's storage profile is PFTT=1, SFTT=1.
- Using VM-to-Host affinity "should" rules to bind the VM to the Preferred-Site.
Just want to see if it is possible for a VSAN Stretched Cluster to automatically vMotion a VM to the other site when for example:
- SFTT in the Preferred-Site becomes non-compliant. E.g., 2 out of 3 components become unavailable (less than 50% votes).
- Or, all 3 components in the Preferred-Site become unavailable (0% votes).
- ...But at least one ESXi host in the Preferred-Site is still running
Normally, with the affinity rule in effect, HA would restart the VM on the surviving ESXi in the Preferred-Site, even if it means the storage traffic has to traverse over the Inter-Site-Link to the Secondary-Site (Where SFTT is still compliant).
Is there a way to make it so that in such scenarios, DRS would just ignore the affinity "should" rule for the VM, and just vMotion the VM across to the other site where the VM's storage traffic could happen locally?
Thanks!