The box that this blog runs on was rebooted this morning, after 272 days uptime and being very reliable. It had to be powered down due to some work in the DC. We should have known about it, but due to us not setting up the email notifications, we were not. The first thing I knew about it was when I was doing a few things and then:
Broadcast message from root (console) (Wed Sep 15 09:57:21 2004):
The system is going down for reboot NOW!
Of course, now we will know if any work needs doing that will need the box to be rebooted. The DC uses a special reboot on demand system to allow for systems to be rebooted at a customers request but I assume they just plugged into the console port to reboot our server, well that is what it looks like from our analysis and what they said when we raised it with them.
The system was only offline for 9 minutes so it wasn't much of an issue that we were not aware of it but good that I happened to be around at the time.
The good thing is we now will know if anything like that needs to to happen again. It also allowed us to ensure the box still comes up, after all the changes that have been made. Soon we're going to upgrade the RAM and probably install another disk too and I'm currently in the process of getting tape backup sorted using Veritas NetBackup which will allow for daily incremental backup as well as a full weekly backup.Post ID: 505, posted by jase at 11:35 PM
Thanks for signing in, . Now you can comment. (sign out)(If you haven't left a comment here before, you may need to be approved before your comment will appear.)