• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 515
  • Last Modified:

Pros and Cons of rebooting a server

Hi All,

I've been asked to right a brief summary of the Pro's / Cons of rebooting servers...


Here are the things i can think of;

> Pros'
Flushes Cache
Restarts services
Clears RAM

> Cons'
Potential system wont come back on
Potentially shortends the life expectancy of the hardware


Any more suggestions.....
0
detox1978
Asked:
detox1978
5 Solutions
 
richwittonCommented:
Takes ages!!!

Seriously though...

Cons
if its the only DC all logon services stop
if its a proxy all browsing stops
if its email all mail stops
if its a file/print server all files or printers are unavailable
0
 
KCTSCommented:
Cons
is rarely necessary
causes disruption to users and potential loss of work

Only do it when you have no other option
0
 
tropez9Commented:
Is required by some Microsoft Updates, so only do reboots when an update is needed, thus limiting the downtime.

CON
If hardware is going to fail, it could very well occur when doing a reboot. (As has happened to 2 hard drives & 1 raid controller on 3 different servers of mine.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
detox1978Author Commented:
Lots of cons.... any more Pros?
0
 
Danny ChildIT ManagerCommented:
if you're going to have a hardware failure on a reboot, I'd much rather have it during some planned maintenance, rather than some other random time!  EVERY server is going to have to reboot at some point.  

I'd disagree with your Con of "shortens life expectancy".  Kit these days is pretty tough, and any talk of thermal issues during power cycles is very overrated, imho.

Pro's
Breeds familiarity with the reboot process, and confidence for further work.  This allows a library of documentation to be built up with tried and tested practices.
Allows testing of related items - such as UPS equipment.
Allows re-adjustment of other items - doing that pesky recabling job behind the server that you've been putting off for months, etc....
Breeds a maintenance culture!  Users will be more understanding that 24*365 availability is just the advertising pipedream that it is.  And you can hardly ask them to reboot every so often if you don't do it yourself....

Things to consider - cluster failover procedures, stopping services in a pre-determined order prior to reboot - ie Exchange services, checking that valid backups exist of the server, that support arrangements are in place, and take notes *while* you do the work - what went well, and what didn't...

Like most things, the more you do it, the better you'll be at it!
hth, Danny
0
 
Danny ChildIT ManagerCommented:
a poll on server reboots (sql-related) - how often, and why....
http://www.sqlserver2005.de/Polls/Results/Poll1.pdf
0
 
detox1978Author Commented:
thanks for the suggestions.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now