[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: migrate to new server - subversion 1.3.0 -> 1.4.3

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-06-29 12:57:57 CEST

On 6/29/07, egoots <egoots@gmail.com> wrote:
> Anne M. Hammond wrote:
> > We currently use subversion 1.3.0 under apache https.
> >
> > I want to migrate to new hardware using subversion 1.4.3/.
> >
> > Is it possible to
> > svnadmin dump
> > svnadmin restore (on the new hardware)
> > cp auth and access file from old server to new hardware
> > then bring up the new hardware using the old hostname and IP address
> > and the users will never know the difference?
> >
> > Or will users have to perform an entirely new checkout of
> > the repos from the new hardware?
> >
>
> The users will also have to upgrade to 1.4.x clients if you upgrade the
> repository to 1.4.x

I think that's only true if you're using file:/// access. Given that
Anne is talking about auth and access files, it's safe to assume that
she's not (as those don't apply to file:///).

> Besides that, I "think" it should work out of the box.
> At worst, you would have to do an svn switch --relocate

If users have any locks on files, I don't think those are included in
the dumpfile.

There isn't (that I recall) an svnadmin "restore" - you need to do an
svnadmin create to create the new repository, then svnadmin load to
put everything in. This will change the UUID of the repository unless
you use --force-uuid, so users will need to do an svn switch
--relocate to pick up the new UUID (I think).

Don't forget to copy your hook scripts too!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 29 12:58:13 2007

This is an archived mail posted to the Subversion Users mailing list.