<slot name="post-flair" class="pdp-flair-slot"><shreddit-post-flair slot="post-flair" post-id="t3_1inkifj"><slot></slot></shreddit-post-flair></slot>
<slot name="mod-content-state-indicators" class="pb-xs"></slot>
<slot name="text-body"></slot>
I have a few questions regarding the vSAN Stretched Cluster setup:
-
Data site-to-data site communication occurs over the vSAN network (vmk1), with data passing between Site 1 and Site 2. However, there is some confusion regarding how this communication flows. Could you clarify?
-
The data site has a management network (vmk0). In addition to this, we can configure "vSAN Witness" traffic on the same vmk0 to ensure traffic separation to connect to witness VM over vmk1(Witness VM(vmk1)-vsan traffic). Is this correct?
-
The Witness VM has two network interfaces:
-
First (vmk0) → Management network, which connects to vCenter.
-
Second (vmk1) → vSAN network, which is used to connect the data sites to the vSAN Witness.(vmk0)
-
Whenever a VM is created on Site 1, its associated storage objects (VM data) are created across Site 1, Site 2, and the Witness (witness components) based on the VM's storage policy. Is this correct?
-
Does all VM-to-VM communication between Site 1 and Site 2 route through the Witness VM (third site), or does it happen directly between the two data sites?
-
In the event of a Site 1 failure, will Site 2 take over automatically with the help of the Witness VM, or does additional intervention/configuration come into play?
<slot name="text-body"></slot>