Date: Tue, 22 May 2007 21:21:40 +0200 From: Volker <volker@vwsoft.com> To: Olivier Mueller <om-lists-bsd@omx.ch> Cc: freebsd-stable@freebsd.org Subject: Re: minimizing downtime on upgrades? (for example: mysql 4.1 -> 5.0 or php) Message-ID: <465342C4.7030306@vwsoft.com> In-Reply-To: <1179860619.14799.37.camel@bigapple.omnis.ch> References: <1179860619.14799.37.camel@bigapple.omnis.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/22/07 21:03, Olivier Mueller wrote: > Some "freebsd-beginner" questions about how to maintain a production > server up to date day after day, with a practical example: now I have > to update a 6.1-based server from mysql 4.1 to mysql 5.0, minimizing > the downtime during the upgrade. > > In the past under other OS'es I would have taken the mysql source, > compiled the whole, and then on upgrade time: > - stopped the services (httpd, etc.) > - mysqldump of all tables > - stopped mysqld > - removed the old version (+backup) > - 'make install'ed the new one > - started mysqld > - imported the db and restarted the other services > -> 2-3 minutes downtime, depending on the size of the databases > > > Now I can't really do that under FreeBSD: if I want to prepare (just > "make" in the ports directory) the mysql50-server part, it answers: > Oliver, try something like: portupgrade -o databases/mysql50-client mysql-client portupgrade -o databases/mysql50-server mysql-server Make sure you're doing a backup of your SQL data *before* you're doing this as the MySQL server (AFAIR) is being halted at upgrade time (short after compiling everything has finished). The portupgrade commands mentioned above might just be half of the work as other ports might need an upgrade, too. I did the same some weeks ago but can't remember if there was any extra work needed. HTH Volker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465342C4.7030306>