Hi everyone! We're in the process of replacing our aging VMware cluster, which has been running for about 7 years, and currently supports around 20 VMs with shared iSCSI storage. We're planning to set up a new 2-node Hyper-V cluster using local NVMe storage and Storage Spaces Direct (S2D). I'd really like to keep both hosts out of a domain, though. Has anyone out there tried this setup with Windows Server 2025 Datacenter? I'd love to hear your experiences or any potential pitfalls to watch out for. Thanks a lot!
3 Answers
I’ve done a similar setup, but honestly, I'd recommend using at least three nodes instead of two. With just two, when you have to do storage repairs, you could be down to a single node of resiliency, which can take ages—up to 10 hours sometimes! Plus, while NVMe is fast, you can still hit bumps during repairs. With three nodes, you maintain better resilience and flexibility. Also, make sure you stagger your updates; I usually wait a whole day between updating each host to avoid downtime issues.
I get the whole non-domain setup, but why not join them? From what I remember, keeping hosts non-domain can lead to issues. I once had a scenario where all virtualized domain controllers were down, and without access to a physical DC, the cluster couldn't reach quorum. It caused a major headache that took a while to resolve.
You'll definitely need a witness for a two-node setup, especially since you're going non-domain. In workgroup scenarios, that witness will be vital, and you might have to use an Azure witness for this. It’s all about maintaining quorum.
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