Date: Thu, 31 Oct 2002 23:56:40 +0100 From: Paul Everlund <tdv94ped@cs.umu.se> To: Steve Warwick <ukla@attbi.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Separating the OS from the data [Addendum] Message-ID: <3DC1B528.9040901@cs.umu.se> References: <B9E6F0A0.3B38%ukla@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Warwick wrote: > [Addendum] > > Cvsup / makeworld: I apologize for missing that piece of information > > Yes, I could use the usual update procedure, however, this is a production > machine. So my thought is: build a new OS on a staging machine, add required > symlinks, pull the drive (sled) and slot it into the production machine. In > THEORY it should be possible to do an upgrade in the time it takes to do a > reboot. For server farms this would be a big benefit... > > > Steve So... Would the following be an option? The production server have two disks: one with the OS on (A) and some symbolic links to another disk where /usr/local is (B). You have another computer with an identical disk (C) as disk A, where you can do the upgrade. Do the upgrade on disk C, pick it out, shutdown the production server, replace disk A with C, and boot the production server. Then put disk A into the other computer and upgrade that disk, then disk A and C will be identical again. Next time, upgrade A and swap it with C. It would be good if you, on the upgrade build computer, could have an exact copy of disk B so you could test, that everything went as expec- ted. Also, it's not necessary to have the mySql database tables in /var. I've put them in /usr/local/mysql, and hence I do not care if anything happens to /var when upgrading. Best regards, Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DC1B528.9040901>