I'm new to the IT industry; I'm not a sysadmin...I'm a road construction guy by trade. So let me know if I've mixed up any terminology, concepts, etc.
My organization's IT department is very small. We seem to be barely treading water when it comes to keeping our IT systems "up".
The thing that causes the most system outages is Windows Server updates. Windows updates seem to bring down our application servers about once per month.
The updates are scheduled to happen automatically -- after-hours on a monthly basis.
Here's an example of a recent outage:
The application server that contains the WebSphere JVMs for our work order management system was automatically updated late at night (via the 1-month schedule).
Today, when users started using the work order management system, we got a bunch of integration/java errors from the JVM.
When investigated, it was clear that issue was caused by the updates. We've never had that issue before, and it happened right after the updates were applied.
Our sysadmin restarted the server, which seemed to solve the issue right away. We dealt with the failed integration messages, etc. and life went on (at least until the next update happens).
I know that my organization isn't the only one that struggles with with windows updates issues. It seems to be a pretty widespread problem.
But my question is:
Are there techniques for handling updates that my organization might have overlooked?
For example, it occurred to me that we could:
- Manually apply the updates and restart the servers on Saturday mornings
- Thoroughly test all of our systems
- Have all weekend to deal with issues and restart servers if we need to (instead of doing it live during business hours).
Are there any standard practices like that for mitigating the risk that comes with updating Windows servers?