Servers and uptime - happy anniversary
At work I manage 7 linux servers. Include estrip and its 8. It seems to be growing but honestly the servers pretty much manage themselves. Managing servers is not really my job but I am good at it and the server techs are mostly a windows group that seem to generally dislike my love for linux. Luckily there is a guy on the network team who is my *nix guru whenever I get stuck. He has servers with years of uptime.
That being said I am getting pretty good at it and I've learned a lot but I have to say, centos itself rocks.
The main web app linux production server I manage at work: 366 days uptime.
Estrip linux server: 369 days
Work linux db server: 76 days would be 366+ but I rebooted 76 days ago to make sure the memory only databases would populate in case of a power failure.
The windows web app servers have tiny uptimes in comparison. For example our main windows web app server is set to reboot every night because no one can figure out the memory issues. It could be the OS, it could be the programs, it could be vendor products, who knows. But one thing is sure, it seems like they constantly need to be rebooted. I am torn on if its windows itself or that no one really understands the windows web servers. I do remember my windows comp needed rebooting all the time too.
Its an interesting situation. The reason the server team loves windows servers is for the support they get from Microsoft.
Its fascinating when I see emails from microsoft support suggesting the solution to a IIS app pool issue is to reboot the server. Is everything in windows solves by rebooting and isn't that a flaw in itself? Isn't the whole point of app pools in IIS to avoid having to reboot the server when apps act up?
That being said I am getting pretty good at it and I've learned a lot but I have to say, centos itself rocks.
The main web app linux production server I manage at work: 366 days uptime.
Estrip linux server: 369 days
Work linux db server: 76 days would be 366+ but I rebooted 76 days ago to make sure the memory only databases would populate in case of a power failure.
The windows web app servers have tiny uptimes in comparison. For example our main windows web app server is set to reboot every night because no one can figure out the memory issues. It could be the OS, it could be the programs, it could be vendor products, who knows. But one thing is sure, it seems like they constantly need to be rebooted. I am torn on if its windows itself or that no one really understands the windows web servers. I do remember my windows comp needed rebooting all the time too.
Its an interesting situation. The reason the server team loves windows servers is for the support they get from Microsoft.
Its fascinating when I see emails from microsoft support suggesting the solution to a IIS app pool issue is to reboot the server. Is everything in windows solves by rebooting and isn't that a flaw in itself? Isn't the whole point of app pools in IIS to avoid having to reboot the server when apps act up?