Re: WSUS/RebootJun 19 2005 11:20AM Martin Mewes (mm mewes tv)
Hi,
"Ronald Balk" <r.balk (at) nl.intrum (dot) com [email concealed]> wrote :
> My question is how to handle the server reboots after a installed
> security patch which requires a reboot.
> We hold about 150 servers, mixed Exchange, reverse proxy, Sql
> etc.etc. Whats the best way to manage this ?
Do it on weekends or over night to sheduled times. Write down the
shedules and chat about it with the business part of your facility.
Tell them that there is no way around this. The other hand would be
money they have to spent for desaster recovery if something happens.
They may re-choose times and windows, but in the end no one should
bother or even recognize if a block of servers will be rebooted at 1.30
AM.
Did someone ever tell Microsoft that they should have a look on unixoid
systems. The only scenario a unixoid box _must_ be rebooted is, when
the kernel has been patched or the main glibc must be changed for some
reasons. But even the latter does not mean to always you need to reboot
the system.
It would be a great help just to be in need of re-starting a service
instead of a machine. Because of the latter, most of the most
significant servers in our facility are running unixoid systems,
because there is nothing more valuable like uptime.
"Ronald Balk" <r.balk (at) nl.intrum (dot) com [email concealed]> wrote :
> My question is how to handle the server reboots after a installed
> security patch which requires a reboot.
> We hold about 150 servers, mixed Exchange, reverse proxy, Sql
> etc.etc. Whats the best way to manage this ?
Do it on weekends or over night to sheduled times. Write down the
shedules and chat about it with the business part of your facility.
Tell them that there is no way around this. The other hand would be
money they have to spent for desaster recovery if something happens.
They may re-choose times and windows, but in the end no one should
bother or even recognize if a block of servers will be rebooted at 1.30
AM.
Did someone ever tell Microsoft that they should have a look on unixoid
systems. The only scenario a unixoid box _must_ be rebooted is, when
the kernel has been patched or the main glibc must be changed for some
reasons. But even the latter does not mean to always you need to reboot
the system.
It would be a great help just to be in need of re-starting a service
instead of a machine. Because of the latter, most of the most
significant servers in our facility are running unixoid systems,
because there is nothing more valuable like uptime.
bis dahin/kind regards
Martin Mewes
--
FAQ fuer suse-linux (at) suse (dot) com [email concealed]
-> http://www.suse-faq.de.vu/
FAQ fuer debian-user-german (at) lists.debian (dot) org [email concealed]
-> http://www.de.debian.org/debian-user-german-FAQ/
------------------------------------------------------------------------
---
------------------------------------------------------------------------
---
[ reply ]