I'm currently helping a client who has a 2-node S2D/Hyper-V cluster with a properly configured cloud witness. The issue arises during maintenance when one of the nodes goes down; the Cluster Shared Volumes (CSV) become inaccessible immediately. I suspect the root cause might lie within the network layer, possibly due to RDMA. If anyone has suggestions or insights, I would really appreciate your help!
3 Answers
Honestly, running a 2-node S2D setup can be quite unreliable. I recommend considering a third node to enhance stability, or even switching to a 2-node Hyper-V Replication setup. I've seen many cases where 2-node S2D setups face serious downtimes and resync issues, so transitioning to a more robust solution might be wise.
Check the event log for any errors; that should be your first course of action before diving deeper into troubleshooting.
Don’t forget to run the cluster validation tool! Just a heads up, though—it can bring the environment down temporarily while you test things out.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures