I'm experiencing some problems while trying to live migrate a domain controller (DC) virtual machine (VM) in a failover cluster environment. We have two Hyper-V hosts that are part of a cluster domain, and our cluster storage is set up on a SAN with multiple links and MPIO configured. Currently, there's only one domain controller running as part of this failover cluster on one of the hosts. When I try to migrate this DC VM to the other host, the migration fails catastrophically at around 70%. I notice several VMs show a loading state in the Failover Cluster Manager on both hosts, and the DC VM doesn't start on the second host. It still appears in Hyper-V on the first host, and I can only get it running again by migrating back to the first host. I'm wondering if this failure is due to the fact that I'm using a single domain controller in my cluster setup. I've done some research but haven't found any concrete information on this issue.
5 Answers
I gotta ask, are you sure you’ve done your research? This isn't just bad luck; your design is raising red flags. Maybe find some best practice guides that outline a better architectural approach to this situation.
Honestly, it seems like there's a design flaw in your setup. Relying on a single DC in a failover cluster isn't recommended. You should be aiming to implement at least two for reliability. Doing some research on proper cluster design would be beneficial.
Definitely ensure you've got a backup handy for that domain controller. If you can, look into creating another DC with any available hardware. Running with just one DC can lead to problems, especially in a failover setup.
First things first, make sure to back up your domain controller! It's critical to have a functional DC when working with a Hyper-V cluster, especially since yours is the only one. Migrating a sole DC can lead to problems like the ones you're experiencing. I'd strongly recommend setting up a second DC as soon as possible to avoid these kinds of issues in the future.
It looks like your setup might be a bit flawed. For a Hyper-V cluster to function properly, you need at least two domain controllers for redundancy. Trying to migrate your only DC is risky and could cause those migration failures you've faced. Please check out resources on virtualized domain controllers in Hyper-V to get a better understanding of best practices.
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