I'd like to follow up this thread a bit.
I've done some testing after getting warm with the powershell scripts and setting up a 2-node homelab with only laptops, so using a single NIC for everything. That means that when I pull a plug, they become entirely separated. I set up a VM sharing the VSAN storage and it created an immediate split brain situation where as they did not even try to resync the latest changes done on a shared VM folder.
However, If I just stopped the service on Node2, so that the NIC was still alive, it triggered an exception and a resync when it came back online. The positive thing though, is that the recent changes I had done while VM was running on Node1, were synced to Node2 as it should, not the other way around even if it says "from partner" in the sync script (yes node2 was the partner). Is this because of some shared quorum technique?
I'm rethinking using 2 nodes, if they loose all contact it's split brain for sure. 2-node setup simply needs to stay connected at all times to be practical and that takes away the HA aspect of it for me. I'm having problems anyway with running a failover cluster without DC on 2 small servers, so I'm not sure what I'm gonna do at all.
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software