Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Mar 2008 18:03:31 +0100
From:      Vincent Mialon <vincent@netaktiv.com>
To:        freebsd-stable@freebsd.org
Cc:        Vivek Khera <vivek@khera.org>
Subject:   Re: Upgrading to 7.0 - stupid requirements
Message-ID:  <200803191803.31872.vincent@netaktiv.com>
In-Reply-To: <FF8E3D52-5C7C-43FC-AA54-49B48957ACD5@khera.org>
References:  <867igo3cih.fsf@zid.claresco.hr> <62b856460803190546t4abfcb9fu7d3410646d81b656@mail.gmail.com> <FF8E3D52-5C7C-43FC-AA54-49B48957ACD5@khera.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Le Wednesday 19 March 2008 17:41:21 Vivek Khera, vous avez =E9crit=A0:
> On Mar 19, 2008, at 8:46 AM, Michael Grant wrote:
> > My server is live and serving customers.  I can't afford to take the
> > box down for a whole day while I upgrade ports.  Is there any
> > intelligent way to do this?
>
> Here's what you do:
>
> 1) take one server at a time down from the load balancer/worker pool
> 2) upgrade it
> 3) put it back in service
> 4) go to step 1 until all servers are updated.

Why not installing FreeBSD 7 on a spare server or a workstation ? You can=20
build your own packages, rsync your confs and test.=20

When everything work, delete all packages on the old server. Make a=20
freebsd-upgrade install. Install all your previously builded packages and p=
ut=20
your confs back. The down time should not be too long I gess ?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803191803.31872.vincent>