I'm looking for some insights on whether it's a good practice to take snapshots of Windows servers before applying updates. I'm planning to automate Windows updates across multiple servers, but I've always been concerned about needing to revert back if something goes wrong post-update. With Windows updates feeling more prone to issues lately, I'm curious if others in the community take snapshots beforehand. If you don't, I'd love to hear your reasoning. Also, if anyone has experience with scripting or automating this process, I'm all ears! Cheers!
5 Answers
I always make sure to create a snapshot before installing any updates. It just feels safer to have that rollback option handy, especially given how unpredictable updates can be at times.
I definitely take snapshots and also use Veeam for backups of critical servers. It gives me peace of mind to have both options available.
While snapshots might be helpful, I think a better strategy is to focus on having proper backups and testing updates on a few systems first. If everything runs smoothly after a week, then roll it out to the rest. This way, you can mitigate potential issues without panicking about snapshots.
I automate my updates to trigger after backups run, so I rely on that instead of snapshots. In my experience, most Windows updates don’t cause major issues, and when they do, you can usually just uninstall the troublesome update.
It really depends on your setup. I back up my servers daily, so the risk is lower for my less active ones. For servers that have more frequent changes, I find taking a snapshot before the update is wise. Better safe than sorry!
Exactly! Testing helps ensure you're not dealing with rushed snapshots that may not be necessary.