I got a question last week if vSAN Site Takeover also works with a 2-node configuration, and my answer was: yes, it should work. However, I had never tested it, so I figured I would build a quick lab environment and see if I was right. I recorded the result, here it is! The demo is pretty straight forward, let me describe what you will see:
- 2-node vSAN environment
- 1 VM named “photon-001”
- Photon-001 VM is “stretched” across both hosts and has a witness component on the witness host
- Host “.245” and the witness will fail and the components on those hosts will go “absent”
- Photon-001 VM becomes inaccessible
- We run the site-takeover command, which will reconfigure the Photon-001 VM
- The Photon-001 VM becomes available again and it automatically restarted
many thanks for this video requested in you original post “What do I do after a vSAN Stretched Cluster Site Takeover?”
not mentioned but am I guess right that site takeover will work for both ESA and OSA 2 node clusters?
how to make a rebuild? is there command to rebuild a cluster once witness/data node will become available again? the components rebuild process will start from scratch or system will compare existing components on witness/data node and will try to update it?
Site Takeover is only available in OSA via RPQ, will be available for ESA in the near future. When it comes to rebuilding, it is a full resync: https://www.yellow-bricks.com/2025/12/04/what-happens-after-a-site-takeover-when-my-failed-sites-come-back-online-again/
many thanks. looking forward for a takeover available in ESA!