Vim Cluster Vsan Vc Stretched Cluster System APIs
vSAN stretched Cluster is a specific configuration implemented in environments where disaster/downtime avoidance is a key requirement.
vSAN stretched Clusters with Witness Host refers to a deployment
where a user sets up a vSAN cluster with 2 active/active sites with
numbers of ESXi hosts between the two sites. The sites are connected via a
high bandwidth/low latency link.
The third site hosting the vSAN Witness Host is connected to both of
the active/active data-sites. This connectivity can be via low bandwidth/high
latency links.
Each site is configured as a vSAN Fault Domain. The nomenclature used
to describe a vSAN stretched Cluster configuration is X+Y+Z, where X is
the number of ESXi hosts at data site A, Y is the number of ESXi hosts at data
site B, and Z is the number of witness hosts at site C. Data sites are where
virtual machines are deployed.
The maximum configuration is 15+15+1 (31 nodes).
vSAN Remote Office / Branch Office Deployment, aka ROBO cluster,
is a specific deployment of vSAN stretched cluster. A two-node
vSAN cluster, and a vSphere vSAN witness host appliance as
witness, forms a vSAN ROBO cluster. Copies of vSAN objects
that make up a virtual machine are typically stored in two physical nodes,
if one of the physical nodes is offline, it is still possible for virtual
machines to run using the files located on another physical node. In the
case where the hosts in a two-node cluster are unable to communicate across
the network, the witness serves as a "tie-breaker" to achieve a quorum and
enables the cluster to restart virtual machines impacted by an outage.
Details to deploy a vSAN stretched cluster, please reference to API
VSANVcConvertToStretchedCluster,
and for ROBO cluster, please assign
witness appliance to parameter 'witnessHost', and each physical host stands
for a Fault Domain.
VsanVcStretchedClusterSystem is used to configure and manage vSAN
stretched cluster. The ManagedEntity can be accessed through MOID of
vsan-stretched-cluster-system, through vSAN service at vCenter server
side.