[K12OSN] Upgrade in lab before production

Terrell Prude', Jr. microman at cmosnetworks.com
Wed Mar 10 20:18:01 UTC 2004


Here's how I've done such upgrades, both on Windows and on UNIX/Linux.

Build a server with identical hardware, with two exceptions:  the amount 
of DRAM may be bigger, and your CPUs may be faster.  Ghost your entire 
hard disk over to a second hard disk of equal or greater size, or, since 
we're talkin' GNU/Linux, use dump/restore to do it.  Pop that cloned 
hard disk into your "clone" server, and try out your upgrade.

That's the safest way that I've found to do it, and it doesn't risk 
taking down the production server.  Also, you have a spare server in 
case you have a hardware failure.

--TP

jamie wrote:

>Hey Gang, 
>I wanna test an OS upgrade before I do it on a production server. What's the
>best way of going about this?
>
>I was thinking of installing RH9 on a test box and then maybe scp all the
>files (except /home) from the production box. Maybe I could do some sort of
>rsync diff
>
>Reboot then make sure the machine works. Then trying the upgrade.
>
>Will this work? I want the test machine to be as close the the production
>machine as possible, even though the hardware is different. Thoughts?
>Suggestions?  
>
>Jamie
>
>
>_______________________________________________
>K12OSN mailing list
>K12OSN at redhat.com
>https://www.redhat.com/mailman/listinfo/k12osn
>For more info see <http://www.k12os.org>
>
>  
>






More information about the K12OSN mailing list