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

Re: Keeping a hot/live FSFS repo for failover

From: Mark <mark_at_mitsein.net>
Date: 2006-10-17 08:55:03 CEST

As Ryan suggests, I am using svnsync for this very purpose. You just
need to add creating the svnsync mirror to your repos creation
procedure, create mirrors for repos you already have, and away you go.
 You'll need to trigger svnsync in post-commit and
post-revprop-change.
Currently, I haven't put in a mechanism for reversing the syncing in
the case of a failover (that was not a requirement for this
implementation), but it should be pretty easy. One just has to
manipulate the revprops for rev 0 on the target.

On 10/16/06, Ryan Schmidt <subversion-2006d@ryandesign.com> wrote:
> On Oct 16, 2006, at 21:49, Kyle Kline wrote:
>
> > I'm implementing an SVN repository with a failover on a sibling
> > server (100mbs LAN), built to do failover very very quickly (two
> > identically configured SVN services, with load balancer directing
> > traffic at the primary.)
>
> Have you looked into svnsync already, which is part of Subversion
> 1.4? It won't do everything you want, but might be a better starting
> point.
>
> http://svn.collab.net/repos/svn/trunk/notes/svnsync.txt
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

-- 
Mark
"Blessed is he who finds happiness in his own foolishness, for he will
always be happy."
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 17 08:56:00 2006

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.