Best Practice for Patching Large VM Windows Server
Hi Everyone
I have a Server 2016 Production File Server that needs patching (no databases just mainly video, Adobe CC and Office files). It's a virtual server (vSphere) with about 12TB of data on it.
Was wondering if you could please recommend any best practices to minimise the risk of issues after the updates?
It's too large to snapshot and I don't have the infrastructure to clone it to test updates because it's so large. I have a full tape backup of the server but would take a couple days at least to fully restore if anything went seriously wrong. The data's also replicated to a data centre so in worst case could connect to that over VPN.
Just going through documentation on updates (cumulative and service stack) to see if any issues. Guess there's the Windows update rollback function, but apart from that can't really think of any other precautions I can take?
Many Thanks
I have a Server 2016 Production File Server that needs patching (no databases just mainly video, Adobe CC and Office files). It's a virtual server (vSphere) with about 12TB of data on it.
Was wondering if you could please recommend any best practices to minimise the risk of issues after the updates?
It's too large to snapshot and I don't have the infrastructure to clone it to test updates because it's so large. I have a full tape backup of the server but would take a couple days at least to fully restore if anything went seriously wrong. The data's also replicated to a data centre so in worst case could connect to that over VPN.
Just going through documentation on updates (cumulative and service stack) to see if any issues. Guess there's the Windows update rollback function, but apart from that can't really think of any other precautions I can take?
Many Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.