subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Marcus <marcus.ja...@gmail.com>
Subject Re: Dealing with binaries and migrating a 36G repository
Date Fri, 12 Apr 2013 16:35:03 GMT
Thanks, I'm going to follow Thorsten suggestion.

Andy,
I actually started a migration with svnsync so that I didn't have to worry
about network issues related to transferring a single 36GB file on an
unreliable network. But I ran into this issue: Cannot accept non-LF line
endings in 'svn:log' property  [500, #125005]

I think I'm getting around this with an svnadmin load

Thanks,
James


On Fri, Apr 12, 2013 at 10:09 AM, Andy Levy <andy.levy@gmail.com> wrote:

>
>
>
> On Fri, Apr 12, 2013 at 9:56 AM, James Marcus <marcus.james@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
> well
>

Mime
View raw message