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

Re: Breaking-up Large Repository

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Tue, 14 Jul 2009 10:35:26 -0500

On Jul 14, 2009, at 09:36, Richard Lichvar wrote:

> First, I want to say how valuable the help has been from the people
> on this list re. issues we’ve been having with SVN, particularly
> when the requests are coming from an SVN newbie (actually a day-to-
> day general, mainly Microsoft, sysadmin) who doesn’t deal with SVN
> all the time.
>
> Now, to the question at hand –
>
> We’ve decided to break-up a very large repository (15+ GB)
> containing multiple projects into separate repositories for related
> projects on a new SVN server. We would like to have your advice as
> to the best way to go about this. (The server is already up and
> running with some smaller repositories that have already been
> successfully transitioned.) As mentioned in other posts, one of the
> major challenges we have with the old SVN server is a dire lack of
> disk space.

You can use svnsync to transfer all or part of the repository to
another server. So you can either sync the whole thing to another
server with more disk space and then do your dump, filter and load;
or you can sync just the project you want to extract to the new
server and there's your new repository all ready to go (well, you'd
have to copy over conf files and hook scripts if you have them). At
least, I was led to believe you can now, with the latest Subversion,
sync just a part of a repository; I'm not sure what the syntax for
that is.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371254

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-14 17:36: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.