Rebooting a System Before Maintenance

Tonight, I write this as I update a storage area network and iSCSI drivers on several Windows servers. Before I do any significant maintenance on a system, I reboot it. It sounds odd, and I do this even though it extends the time required for maintenance.

The purpose is to tease out errors before I introduce changes into the system. Occasionally, an error condition reveals itself during this initial reboot. This is a good thing because now I know that the error can’t be attributed to the change(s) I was about to make. Had I made my changes and then rebooted the system, it would have complicated the troubleshooting process because I wouldn’t know if the condition existed before the change, or if the change I made caused the condition. This allows me to resolve any issue(s) before continuing with the maintenance and it simplifies the troubleshooting process when problems exist.



Google