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

RE: Estimation of repository upgrade

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Fri, 5 Aug 2011 13:19:50 -0400

> On Fri, Aug 5, 2011 at 12:19 PM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
> >> On Fri, Aug 5, 2011 at 10:58 AM, Bob Archer <Bob.Archer_at_amsi.com>
> wrote:
> >>
> >> > Has anything been done to improve the speed of a load. Last time I
> >> > did it,
> >> when moving from 1.5 to 1.6 it took over 12 hours. And now, two years
> >> later the repo is probably quite a bit bigger (because we stupidly
> >> store binaries in it, I might change that when upgrading to 1.7).
> >>
> >> You can pre-configure by using svnsync to pre-create a new
> >> repository, and replicate relevant configuration files or scripts
> >> manually when ready to switchover. This is what I've used for
> >> migrating between servers that do not have shared back end storage,
> >> especially when updating operating systems and Subversion releases on
> the servers.
> >
> > But, doesn't that change the GUID of the repository thus not allowing a
> relocate switch?
>
> Until you manually copy over the $repodir/db/uuid file, this is true.
> That's one of the "relevant configuraton files" I referred to.

So, are you saying svnsync will be faster than a dump/load?

I didn't know the guid was stored in a file.

BOb
Received on 2011-08-05 19:20:25 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.