witness

2-node vSAN – witness network design considerations

It seems that 2-node vSAN for ROBO (remote office/branch office) deployments are becoming more and more popular. The fact that one can now connect the 2 vSAN [...]

New vSAN Stretched Cluster Topology now supported

After publishing the vSAN Networking Guide earlier this year, Paudie O'Riordain and I received numerous questions regarding support on having different [...]

Erasure Coding and Quorum on vSAN

I was looking at the layout of RAID-5 object configuration the other day, and while these objects were deployed on vSAN with 4 components, something caught my [...]

Why two stretched clusters cannot cross-host each others witness appliances!

Sorry about the wordy title but this is a question that has come up a number of times. The request is that when I have two data sites and deploy two stretched [...]

2-node vSAN topologies review

There has been a lot of discussion in the past around supported topologies for 2-node vSAN, specifically around where we can host the witness. Now my good pal [...]

Another recovery from multiple failures in a vSAN stretched cluster

In a previous post related to multiple failures in a vSAN stretched cluster, we showed that if a failure caused the data components to be out of sync, the most [...]

Understanding recovery from multiple failures in a vSAN stretched cluster

Sometime back I wrote an article that described what happens when an object deployed on a vSAN datastore has a policy of Number of Failures to Tolerate set to [...]