I am limited to a narrow window for reboot which is between 2:00 AM - 3:30 AM on Monday morning only. That's the only morning we don't perform a backup. As for a server not comming back up...We have a 24/hr in-patient unit that must document patient care. If the server doesn't come back up, the nurses detonate a load of C-4 hidden in my on-call cell phone as soon as I flip the phone open.
MTTF (Mean Time To Failure) on a drive is usually 1.4 million hours. That's lab time. In a recent study of 70,000 drives in real world use you divide the 1.4 million (lab time) by 14 and that give you real-world MTTF of 100,000 hours. Divide this by 24 = 4,166 days MTTF or 11.4 years MTTF. Laboratory MTTF testing includes stress testing, power on/off,sudden power loss,etc.
I think the amount of degredation from re-booting is minimal and the benefits are maximum. This is a Citrix server. I estimate the Business Interruption at about $1,000/hr when it crashes.
I think my Network Admin is short a packet or two in his thinking.
I've got references for my stats if anybody wants em.
Any comments?
Phred
DBA
BTW I think your statement is very astute, "I think not rebooting regularly could cause more problems then rebooting."
I'm adding some stuff to my post. MTTF is a statistical method of forecasting failure. It does not mean a drive will last 11 years. If MTTF is 1.4 million hours the statistic means if you took 114 drives and ran them for one year you could expect 1 drive to fail during that time.
The above is a lousy paraphrasing of article by Adrian Kingsley-Hughes, March 2007, http://blogs.zdnet.com/hardware/?p310, Making Sense of "Mean Time to Failure."
My apologies to Adrian.
An excellent article is from the Parallel Data Laboratory at Carnegie Mellon University. "Disk Failures in the Real World" Bianca Schroeder, Garth Gibson, September 2006.