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

Re: Dealing with binaries and migrating a 36G repository

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 12 Apr 2013 10:09:08 -0400

On Fri, Apr 12, 2013 at 9:56 AM, James Marcus <marcus.james_at_gmail.com>wrote:

> Hi,
> I have been trying to migrate a hosted repository that is 36G. This is
> difficult because we have offshore teams, so the repository is almost
> always active. Before I got here, it seems that someone had the build
> process check in each binary after it was built.... Urgh!
> I'm looking for tips on migrating this repository?
> I have a list of the revisions that are greater then 10M
> I have looked for svndump filters to exclude certain revisions, and
> considered other migration paths, but exporting 36G then scp'ing it off to
> another host takes a long time and I think it would be best if I could
> export everything except the binaries.. Is there a way to do this with
> svndump?

Could you do this?

1) Dump the current repository up to a revision after the point where
people stopped committing binaries in the build process
2) Filter out the revisions from the dumpfile
3) Load the result into a repository on the new server
4) Use svnsync to catch the new repository up (and keep in sync)
5) Cut over to the new server when you're satisfied everything is running
Received on 2013-04-12 16:10:21 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.