On Fri, Sep 26, 2008 at 08:55, David Aldrich <David.Aldrich_at_eu.nec.com> wrote:
> Hi
>
> We are planning to upgrade our svn server from 1.4.6 to 1.5.2. We are
> checking what is necessary to be done and would be grateful for comments on
> our plan.
>
> We have multiple repositories (one for each of our projects) in FSFS format.
>
> The plan is:
>
> 1) Install svn 1.5.2 onto new server hardware, running under Centos 5.0
>
> 2) Notify users and disable access to 1.4.6 server
>
> 3) Backup each repository using 'svnadmin dump' (or could use tar - I) and
> restore onto the new server
>
> 4) Run both svnadmin upgrade and svn-populate-node-origins-index on each
> repository
If you use svnadmin dump in 1.4.6 on the old server and svnadmin
create + svnadmin load in 1.5.2 on the new server, then step 4
shouldn't be needed.
> 5) Map existing http: url to point to new server
>
> 6) Notify users that new server is up and running.
>
> Users will remain at 1.4.6 client for now. I see no reason for them to
> commit modified files prior to the upgrade.
>
> Some file locks may be active, do we need to look after those in some
> special way?
Locks aren't maintained in the dumpfile. My personal preference would
be to get people to release all their locks (thus committing their
changes as well). I'm not sure if there's a "right" way to carry them
over.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-26 17:15:05 CEST