Only one problem with SVN::Mirror... try the following:
On the master repository:
1) create a test folder in svn: e.g. /trunk/Test
2) Add 100MB file to /trunk/Test/BigFile.bin
3) Now mirror the master repository to the mirror repository using
SVN::Mirror.
Again on the master repository:
4) Execute svn cp /trunk/Test /trunk/Test2
The master repository is now still just over 100MB.
5) Now use SVN::Mirror to update the mirror repository.
To your dismay you will find that your mirror repository is now 200MB in
size, and doesn't correctly show the svn cp, but instead makes it look like
a new 100MB file was added to /trunk/Test2.
I did this with SVN::Mirror 0.29.
I've manually worked around this by avoiding SVN::Mirror altogether, and
using ssh from the mirror repository to incrementally request dumps (using
svnadmin dump from the master repository, scp to transfer those dumps to the
mirror repository, and then svnadmin load to load those dumps into the
mirror repository).
If you need details, I can freely post the scripts and describe the configs
used. In my case I want the mirror repository to be an *exact* replica of
the master repository (for disaster recovery purposes, etc.) so mirroring
the way SVN::Mirror works didn't meet my requirements.
> -----Original Message-----
> From: John Peacock [mailto:jpeacock@rowman.com]
> Sent: 07 April 2004 05:11 PM
> To: Euan Guttridge
> Cc: users@subversion.tigris.org
> Subject: Re: 2 teams 1 server
>
> Euan Guttridge wrote:
>
> > Does SVN support replication of any sort? Objective is to find an SCM
> that
> > will syncronize two or more remote servers at regular intervals. Problem
> > being if 70 devs are on each remote site, it would be too expensive for
> all
> > devs to syncronize 100MB code base.
> >
> > I searched archives, no joy.
>
> You should see if SVN::Mirror will do what you want; this allows you to
> mirror
> the repositories, without the overhead of svk. There was also a
> SVN::Push, I
> believe, which did something similar. It really depends on how closely
> the two
> sites are intertwined in their development (i.e. are changes required to
> be
> propagate to both systems immediately, or would nightly syncs be
> sufficient).
>
> John
>
> --
> John Peacock
> Director of Information Research and Technology
> Rowman & Littlefield Publishing Group
> 4501 Forbes Boulevard
> Suite H
> Lanham, MD 20706
> 301-459-3366 x.5010
> fax 301-429-5748
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 7 17:18:45 2004