[Gllug] best way to update a single production server?

[Alain Williams]

On Fri, May 01, 2009 at 11:21:02AM +0100, Khusro Jaleel wrote:
> Hi everyone,
> 
> We have a very important production server that needs updates (just
> simple Debian Etch updates, not Etch to Lenny). There are several
> updates, including kernel and other updates, etc.
> 
> Since unfortunately we have only this server, and it MUST be up 24/7,
> I'm not sure how to apply these updates, since a reboot is needed.

If ''it MUST be up 24/7'' then what are you doing only having one server anway ?
That server could be taken out by the sudden death of a disk/psu/... or even
total loss of connectivity to the data center.


> In the longer term, what is the proper way to manage this process? Do
> you guys always install 2 servers in some sort of HA config so that
> while 1 is being updated, the other one takes over?

It all depends on what ''MUST'' really means. If it is really valuable then the
funds to make it robust are surely available.

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php
Past chairman of UKUUG: http://www.ukuug.org/
#include <std_disclaimer.h>
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug