On 19/04/10 10:00, Andy Bennett wrote:
These days system stability seems to be actively
discouraged in a
flurry of changes and tweaks. Worse, often these changes are couched
in terms of those factors but without any clear indication that there
is a problem or the problem is big enough to warrant the disruption
caused by the "fix".
My friend's company once "lost" a server. They could ping it but no
one could remember where it was. Eventually they discovered that it
had been plastered up behind a partition during an office
refurbishment a few years previously.
Surely this is an anecdote which would make any good sysadmin recoil in
horror?!
Imagine running important services on such a server and it blowing a
power supply. I wouldn't want to be the person to explain to the MD of
the company that not only was an important service not running, that I
couldn't even locate the machine it was supposed to be running on. Inept
doesn't even begin to describe it.
(It sounds apocryphal to me anyway, but it would certainly be a good
example of 'worst IT practice' I could think of)
Cheers
Alex.
--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com