[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: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Fri, 12 Apr 2013 16:08:01 +0200

Guten Tag James Marcus,
am Freitag, 12. April 2013 um 15:56 schrieben Sie:

> I'm looking for tips on migrating this repository?

Dump it, copy it where ever you want and afterwards use svnsync to
keep it a current read only mirror until you are able to switch to the
new repo.

> I have looked for svndump filters to exclude certain revisions, and
> considered other migration paths[...]

Using svndumpfilter means that you need to checkout a new working copy
for everything you have working copies now. Not only users, even build
systems or whatever.

Depending on when you did the last dump-load-cycle of your repos, it
may be enough to just create new repos as current versions of svn
provide representation sharing of binaries which may save you a lot of
space. Just test it locally.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2013-04-12 16:08:29 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.