Windows Server Restarts
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
For IIS running well tested ASP.Net applications and SQL server almost never. NT4.0 server application running VB COM components, or any app using Oracle database drivers, then nightly reboots are very helpful. The OS is stable, but some extra services like COM+ and Exchange aren't up to the same level of quality.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
Paul Watson wrote: our Windows server (Exchange and SQL) needed to be rebooted about once a week What was wrong with it that it required a reboot? Perhaps it just needed more memory or something...? (Wild guess) I have a 2003 server (500mhz PII, 256mb RAM) runnning IIS, SQL Server, Mail Server, File Server, Print Server, Domain Controller and occasionally BitTorrent, and I haven't restarted it for months. Sure BT can load it down a bit, but as soon as I close the program, it perks right up again...
Miszou wrote: I haven't restarted it for months. Living dangerously? I assume this means you do not apply service packs / updates ... John -- modified at 16:18 Wednesday 5th October, 2005
-
Well we ran Windows and Linux servers in my old job and the Linux server (handling email and all internet traffic) never needed to be rebooted while our Windows server (Exchange and SQL) needed to be rebooted about once a week. But then that is probably more Exchange for you... god, that Exchange Store service was wild. regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
Paul Watson wrote: Linux servers in my old job and the Linux server (handling email and all internet traffic) never needed to be rebooted Sign of a bad admin in my opinion. I wonder how many security patches and kernel patches where not put onto that machine. When it comes to security prevention is a lot better then cure in my opinion. It is perfectly possible to have a site/service up constantly and still apply patches and reboot machines as long as you have at least a single layer of redundancy. Just use a reverse proxy/router configuration to point packets to the backup machine while the patches are applied to the main server and it restarted... this applied to both windows and linux servers of course. Regards, Brian Dela :-) Blog^ Co-author of The Outlook Answer Book... Go on, order^ it today!
-
Paul Watson wrote: Linux servers in my old job and the Linux server (handling email and all internet traffic) never needed to be rebooted Sign of a bad admin in my opinion. I wonder how many security patches and kernel patches where not put onto that machine. When it comes to security prevention is a lot better then cure in my opinion. It is perfectly possible to have a site/service up constantly and still apply patches and reboot machines as long as you have at least a single layer of redundancy. Just use a reverse proxy/router configuration to point packets to the backup machine while the patches are applied to the main server and it restarted... this applied to both windows and linux servers of course. Regards, Brian Dela :-) Blog^ Co-author of The Outlook Answer Book... Go on, order^ it today!
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
Miszou wrote: I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Nope, we haven't restarted our win2k and win2k3 servers in months and only if there is some reason to such as a software update etc. One is an IIS forum server primarily, one is an in-house biz server and the other is a development and testing server. There should really be no reason to do this AFAIK, there wasn't even in the NT4 days either so someone is being superstitious or there is a mis-behaving driver involved perhaps.
"A preoccupation with the next world pretty clearly signals an inability to cope credibly with this one."
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
Never restart them except for drivers. Never need too either. I cant recall when last I have seen a BSOD. :p I dont experience slowdowns either. I guess 1GB RAM does the trick. :) xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots
-
Paul Watson wrote: Linux servers in my old job and the Linux server (handling email and all internet traffic) never needed to be rebooted Sign of a bad admin in my opinion. I wonder how many security patches and kernel patches where not put onto that machine. When it comes to security prevention is a lot better then cure in my opinion. It is perfectly possible to have a site/service up constantly and still apply patches and reboot machines as long as you have at least a single layer of redundancy. Just use a reverse proxy/router configuration to point packets to the backup machine while the patches are applied to the main server and it restarted... this applied to both windows and linux servers of course. Regards, Brian Dela :-) Blog^ Co-author of The Outlook Answer Book... Go on, order^ it today!
Well, this is not really an excuse but anyway, I didn't manage it. It was done by a chap 10,000 kilometeres away in London. He was not very communicative. Me in a tentative email: Hey, linux dude, could you check the linux box please? Linux dude: Sw33t, n0 pr08l3m w1nd0z3 a8bu5r! Ha! H3ll 5pawn! Check it yourself you GUI freak. Me: Listen, fix it and we pay you, don't fix it and you can go back to packing boxes at the local newspaper office, ok? Also all I knew about Linux back then was that it was written by a bunch of penguins. Now I know it was written by a penguin named Linus. BTW I am digging Ubuntu. Great Linux distro. So I am not being a lame Windows user. :) regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN! -- modified at 17:11 Wednesday 5th October, 2005
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
I run several Win2k servers. I can only remember one instance in the last two years that I had to reboot a server that was not a part of planned maintenance/patching. I almost never have to restart a server for issues other than dropping patches, new software, etc. The one time I did have to restart was not due to the OS being unstable but was because the exchange information store had issues. Jim
-
Never restart them except for drivers. Never need too either. I cant recall when last I have seen a BSOD. :p I dont experience slowdowns either. I guess 1GB RAM does the trick. :) xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots
You only have a gig of ram in your server? ;) regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
You only have a gig of ram in your server? ;) regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
No, just my dev/personal PC, server has less :) xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots
-
-
So if you install a Linux patch that doesn't require a restart you may be less secure than the same box with the same patch but restarted? regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Well, this is not really an excuse but anyway, I didn't manage it. It was done by a chap 10,000 kilometeres away in London. He was not very communicative. Me in a tentative email: Hey, linux dude, could you check the linux box please? Linux dude: Sw33t, n0 pr08l3m w1nd0z3 a8bu5r! Ha! H3ll 5pawn! Check it yourself you GUI freak. Me: Listen, fix it and we pay you, don't fix it and you can go back to packing boxes at the local newspaper office, ok? Also all I knew about Linux back then was that it was written by a bunch of penguins. Now I know it was written by a penguin named Linus. BTW I am digging Ubuntu. Great Linux distro. So I am not being a lame Windows user. :) regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN! -- modified at 17:11 Wednesday 5th October, 2005
a8bu5r I can normally read and write 1337 with the best of them...but what the heck is that supposed to be? Abuser?
Picture a huge catholic cathedral. In it there's many people, including a gregorian monk choir. You know, those who sing beautifully. Then they start singing, in latin, as they always do: "Ad hominem..." -Jörgen Sigvardsson
-
No, just my dev/personal PC, server has less :) xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots
Your personal PC only has 1 gig of RAM? :rolleyes:
Picture a huge catholic cathedral. In it there's many people, including a gregorian monk choir. You know, those who sing beautifully. Then they start singing, in latin, as they always do: "Ad hominem..." -Jörgen Sigvardsson
-
a8bu5r I can normally read and write 1337 with the best of them...but what the heck is that supposed to be? Abuser?
Picture a huge catholic cathedral. In it there's many people, including a gregorian monk choir. You know, those who sing beautifully. Then they start singing, in latin, as they always do: "Ad hominem..." -Jörgen Sigvardsson
Errr... yeah... abuser... not abbuser :-O regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
With Windows 2000 and XP I only restart my PCs when specifically needed, they keep running without problems. I don't have a server. Elaine :rose: The tigress is here :-D
-
So if you install a Linux patch that doesn't require a restart you may be less secure than the same box with the same patch but restarted? regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Your personal PC only has 1 gig of RAM? :rolleyes:
Picture a huge catholic cathedral. In it there's many people, including a gregorian monk choir. You know, those who sing beautifully. Then they start singing, in latin, as they always do: "Ad hominem..." -Jörgen Sigvardsson
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
I manage 11 servers. 8 are Windows Server 2000 and 3 are Windows Server 2003. 6 of these are off-the-shelf Dell servers, 4 are custom built servers and 1 is an old phone system server that started out life as Windows NT 4.0 before I worked at the company. All but one of these servers is rebooted once a month so that I can install system updates, cleanup event logs, temp files, etc. The other server is rebooted once a week because it is a development server and some of the apps running on it (I wrote them) are not exactly "production ready". In the past 3 years I can't remember any non-hardware related situations that caused one of these servers to be unstable or crash.
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
Our servers are rebooted for service packs but that is about the extent of it. The *nix servers come down just as often. Only difference is that the *nix admins never admit it. They just say they slowed down! We also have NT machines (W2K) that house the ISAPI plugin for websphere which has to be rebooted a little more often. Like twice a week. That matches your first reason. I don't really think windows is as bad as the press it gets. It's generally the apps that get installed subsequently IMHO. As far as my own machine...any time I read a PDF it's time to reboot. Acrobat just kills it! ed ~"Watch your thoughts; they become your words. Watch your words they become your actions. Watch your actions; they become your habits. Watch your habits; they become your character. Watch your character; it becomes your destiny." -Frank Outlaw.