On Fri, Mar 2, 2012 at 9:25 AM, Les Mikesell <lesmikesell@gmail.com> wrote:
On Fri, Mar 2, 2012 at 10:20 AM, Geoff Hoffman
<ghoffman@cardinalpath.com> wrote:
>
>> > I created the mirror repository fine, ran svnsync init and svnsync sync
>> > on
>> > it, then as it started going from -r 1, -r 2, -r 3..., I realized it
>> > would
>> > take a week or more to fetch all nearly 4K commits.
>>
>> Slow is one thing - but that sounds unreasonable.  Is there some
>> network issue involved?  Maybe you can svnsync on a nearby machine,
>> then copy or move the resulting repo once it is caught up.
>>

> The speed issue is that I'm storing the mirror repo on a slow computer, on a
> USB Drobo that is in turn being backed up to an online backup service.

But you should be able to copy a whole repo, maintaining state as long
as the target is reasonably similar.  I see you have gotten it to work
another way, but you should have been able to do the initial catch-up
sync on something faster, copy that repository where you want it, then
resume the syncs to keep it updated.


This is pretty much exactly what I did, Les.  

My other question from my initial post is, should I be doing it in exactly this order:

// source-server
1. svnadmin dump source-repo > source.dump
2. tgz it and scp it to mirror-server
// mirror-server
3. svnadmin create mirror-repo
4. svnsync init here !!  // this is what I didn't do before
5. svnadmin load ? or do you have to just let it sync from -r 0 

With 1.6x and before, it may be just as easy to issue 3 propsets as above. I think I'll write a blog post on this. There doesn't seem to be a single concise procedure outlined anywhere on the net. Although, it's nice to learn that svn 1.7+ added the --allow-non-empty option.


This email, including any attachments, is for the sole use of the intended recipient and may contain confidential information. If you are not the intended recipient, please immediately notify us by reply email or by telephone, delete this email and destroy any copies. Thank you.