I'm in the process of transitioning from an old VMware setup to a single Hyper-V host that will run several VMs, including our Domain Controller and radius server. I'm looking for advice on how to approach patching the host while managing possible downtime for these critical infrastructure servers. Additionally, I'm curious about strategies for recovery if anything goes wrong during the patching process.
4 Answers
With a single Hyper-V host, your best bet is to shut down all your VMs, apply the patches, reboot, and cross your fingers. It doesn't sound like there’s much redundancy in your setup, so you'll need to plan for some downtime during this process.
If you’re running a single host, it’s all about timing. Patch during a maintenance window—maybe after hours or late in the day when impact will be minimal. Make sure your users know when to expect downtime. Also, get a script together to shut down your VMs properly.
I’m not sure where the confusion is, but the patching process can be straightforward. Just set up a script to shut down the VMs in the right order, run your patches on the host, and then bring the VMs back up in reverse order. Easy peasy!
For more critical setups, I usually schedule patches during off-hours. I might run updates just before midnight when there’s minimal activity, ensuring the Domain Controller is always functional by staggering patches across different times.
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