I'm currently managing a 2-node, non-domain-joined Hyper-V and S2D cluster for a project, and it needs to maintain almost zero downtime for an important application. Next week, I'm planning to do a rolling OS and hardware upgrade. I want to know whether I should convert the cluster from its current DNS setup to an Active Directory (AD) one once the upgrade is completed. I understand that this migration will likely involve some downtime, but I'm curious about how much downtime I should expect. Any insights would be appreciated, as I'm new to working with Windows clusters!
3 Answers
Sticking with a DNS cluster is like trying to pay bills with Monopoly money. Sure, it can handle things temporarily, but you’ll likely run into issues down the line, especially with cluster communications. Just bite the bullet, join the domain, and save yourself the grief when something goes wrong in the middle of the night.
My top tip: definitely domain join your Hyper-V hosts. It streamlines management and reliability. Going with a DNS-only setup is risky; it might work just fine until it doesn’t, which could lead to headaches later on. Expect about an hour of downtime during the migration, which is manageable when you plan for it.
Honestly, that 2-node S2D setup is just a pain in the rear end. You might want to reconsider the design if you have a chance—or if not, just ensure you’re prepared for the quirks that come with it. Joining the domain can help mitigate some of these struggles.
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