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

Jose Luis Martinez jjllmmss at googlemail.com
Fri May 1 14:06:10 UTC 2009


On Fri, May 1, 2009 at 11:37 AM, Martin A. Brooks
<martin at hinterlands.org> wrote:
> On 01/05/2009 11:33, Alain Williams wrote:
>> It all depends on what ''MUST'' really means. If it is really valuable
>> then the
>> funds to make it robust are surely available.
>>
>
> All too often a server MUST be up 24/7 -because- the funds to make it
> robust are not available :)
>
>
> --
> Gllug mailing list  -  Gllug at gllug.org.uk
> http://lists.gllug.org.uk/mailman/listinfo/gllug
>

I don't agree with that.

We are professional IT specialists, I personally don't convert water
in wine, no matter how much I would like to be able to do so.

With such a weak system I would make clear that the 24 hours uptime is
just not achievable and would put in place maintenance windows during
which the server could be down. Depending on pay, the support window
could be at the quietest time of the day, but if the pay was lousy,
the maintenance window would be just before or after the normal
working day (to the kids out there starting in this field: don't
accept to be exploited, stand you ground and make sure you are
compensated properly for working unsocial hours).

The only way that people relying on such system stop to believe in
miracles is for the Sys Admin to stop trying to walk in water.
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug




More information about the GLLUG mailing list