On Tue, Jul 08, 2003 at 08:22:58AM -0700, Nichols, William wrote: > Currently I have my Live box, and a warm box, they both stay config'd > the same, when new SA comes out, I prep it on the warm box, move all > incoming mail to that server, then update the live box and move the mail > to come back through it. Doesn't seem that efficient, I am just > wondering what others do.
That seems like a "production" style environment to me. Upgrade on the
backup box, do testing, make sure everything works, "fail over" to the
backup, wait, upgrade the primary, do testing, make sure everything works,
"fail back" to the primary.
No downtime, and easy back out if the backup box starts showing issues.
I only have 1 box at any given location to deal with, so my procedure
tends to be along the lines of: read the documentation, declare a period
of downtime, shutdown SA, upgrade SA using my favorite method (I do RPM,
but tarball, CPAN, etc, is fine too), follow the upgrade directions in
the release announcement if any, make sure the new config is working,
do testing, make sure everything works, start SA.
--
Randomly Generated Tagline:
"The user's computer downloads the ActiveX code and simulates a 'Blue
Screen' crash, a generally benign event most users are familiar with
and that would not necessarily arouse suspicions."
-- Security exploit description on http://www.zks.net/p3/how.asp
pgp00000.pgp
Description: PGP signature
