This content has been marked as final. Show 9 replies
Hmm, check the hardware so that you don't have servers running with broken disks or other broken components. Its fairly common for unmaintained systems to have broken disks, which isn't noticable as long as the remaining disk/part doesn't fail..1 person found this helpful
Lol, of course. I edited the above list with your tip. Thanks.
Create a "runbook" for each server.1 person found this helpful
...1 person found this helpful
Consider grabbing a snapshot of mounted filesystems, runnng services, and running processes.
... If the machine gets rebooted (either planned or unplanned) you may have an indicator it has not reached the expected state.
... Try to identify anything that has to be manually restarted on reboot.
.. such as Sun's Explorer tool :)1 person found this helpful
Yes, a runbook is a great idea. I'd like to start compiling that fairly early in taking over support of these, although I suspect it will be on of the last things completed.
You know, I had thought of the rest of the things you mentioned, but the snapshot had escaped me. That's a great tip, thanks.
Sorry, I'm not familiar with Sun's Explorer tool in this context. What are you worried about, it not restarting?
You cross-posted this to other forum web sites
... and didn't have the manners to mention that fact so that people wouldn't have to spend time formulating a response that duplicates what you've already been told in those other forums.
This thread is locked.