On a vSAN stretched cluster, DRS automatically favours the site that can serve reads locally when it places VMs. After an HA restart, VMs do not move back until resynchronisation is complete. No configuration is offered.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains DRS Awareness of vSAN Stretched Cluster in context, with comparison tables and the common traps.
Terms in this definition
- vSAN stretched cluster
Spreads a vSAN cluster's hosts equally across two availability zones, with a separate witness placed in a third location, keeping data available even when an entire site fails.
- DRS
The Default Rule Set, Microsoft's managed WAF rules that succeed OWASP CRS and defend against XSS, SQL injection and other frequent attacks. Single rules may be overridden or switched off.
- LSDOU
The sequence in which Group Policy is processed: the local policy first, followed by site, domain and organisational unit policies. The nearest, last-processed setting takes effect unless Enforced or Block Inheritance alters that.
- Virtual machines
Infrastructure-as-a-service compute giving complete control of the operating system, making it a fit for lift-and-shift moves and for software relying on OS-level pieces like COM.
- resync
vSAN's repair activity, in which components of objects are rebuilt or relocated so they meet policy again. Causes include device, host or network failure (after the repair delay), maintenance mode, policy edits and rebalancing; watch it under Monitor > vSAN > Resyncing Objects.
- Deployment modes
The two ways ARM can deploy: Incremental, the default, creates or updates what the template lists and ignores everything else; Complete also removes resource group contents absent from the template.
See DRS Awareness of vSAN Stretched Cluster in the full glossary