It is possible to deploy vSAN in unusual, or corner-case configurations.

These unusual topologies require special considerations.

Three Locations, No Stretched Cluster, Distributed Witness Hosts

You can deploy vSAN across multiple rooms, buildings or sites, rather than deploy a stretched cluster configuration.

This configuration is supported. The one requirement is that the latency between the sites must be at the same level as the latency expected for a normal vSAN deployment in the same data center. The latency must be <1ms between all hosts. If latency is greater than this value, consider a stretched cluster which tolerates latency of 5ms. With vSAN 6.5 or earlier, additional considerations for multicast must be addressed.

For best results, maintain a uniform configuration across all sites in such a topology. To maintain availability of VMs, configure fault domains, where the hosts in each room, building, or site are placed in the same fault domain. Avoid asymmetric partitioning of the cluster, where host A cannot communicate to host B, but host B can communicate to host A.

Two-Node Deployed as 1+1+W Stretched Cluster

You can deploy a two-node configuration as a stretched cluster configuration, placing each host in different rooms, buildings, or sites.

Attempt to increase the number of hosts at each site fail with an error related to licensing. For any cluster that is larger than two hosts and that uses the dedicated witness appliance/host feature (N+N+Witness, where N>1), the configuration is considered a vSAN stretched cluster.