I need to upgrade a live system, and I wonder how people tackle this
problem. The system hosts users and their websites, email and several other
services. I need to perform a full OS upgrade (mainly because I'm more
comfortable doing that, than the usual Upgrade path), so naturally the system
will be down for quite some time while I reload a new OS, download and install
erratas, perform security updates, blah blah blah, before finally putting it
back online. Doing this will also nuke the system's SSH keys, causing everyone
to have to generate new ones. And I'm not sure yet how to deal with having to
recreate people's logins - not sure if just pulling /etc/passwd, shadow and
group files from backup and dropping them back in place is all that needs to
happen.
How do you folks deal with having to take the system down to perform an OS
upgrade, without much of a downtime to your users? Overnight? And what
happens if you run into trouble? How do you (politely) tell your users they
can't access their accounts till the system is done being rebuild.
Also, what happens with the Apache SSL key that was once generated and used
to acquire a Thawte certificate? I have the files that were used, but I'm not
sure how to redo that without screwing up the certificate (and consequently
having to buy a new Thawte cert.)
--
W | I haven't lost my mind; it's backed up on tape somewhere.
+--------------------------------------------------------------------
Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
IT Director / SysAdmin / WebSmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
