RE: SVNSYNC Error

> On Wed, Aug 1, 2012 at 5:14 PM, Stefan Sperling <stsp_at_elego.de> wrote:
>
>
> On Wed, Aug 01, 2012 at 04:57:57PM +0800, Honeylyn O.
> Fukuoka wrote:
> > Hi,
> >
> > Thanks for this.
> > We are using snserve not Apache...
> > Will this link still work with us?
>
>
> Sure. svnsync is just about repository replication, and
> has nothing
> to do with what server is being used to allow access to
> the repository
> via the network.
>
> You didn't mention why you want to use svnsync. If your
> goal is to back
> up a repository to another machine then all you need is svnsync.
> If the goal is to set up a write-through proxy using
> the mirrored repostory
> then you need svnsync and Apache HTTPD because svnserve
> doesn't support
> write-through proxying.
>
> -----Original Message-----
> From: Honeylyn O. Fukuoka [mailto:honeylyn_at_menue.com]
> Sent: 01 August 2012 13:15
> To: Honeylyn O. Fukuoka; David Chapman; vishwajeet singh;
> users_at_subversion.apache.org
> Subject: Re: SVNSYNC Error
>
> Hi,
>
> The reason why I am doing the svnsync is to backup our
> repository to our new server in our main branch.

If all you are doing is a one-off move, then you should also investigate using dump/load. Depending on the size of your repo this can take a while, but can be done without svnsync and can have advantages in having your shiny new in the latest format.

I suggest that you read the manual, especially this bit about "Migrating Repository Data Elsewhere":-

http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate

~ mark c

P.S. It is often good to explain what you are trying to do before asking for specific help. This helps us to discuss other, better ways to do stuff than you know about...
Received on 2012-08-01 14:29:39 CEST