DRBD seems like it would be overkill for his purpose. If you only
need SVN repositories mirrored, svnsync does the trick. Plus, at a
glance in the DRBD docs I didn't see how well it fares over long WAN
distances. In my situation, my primary and secondary server are 1500
miles apart.
as far as svnsync creating a 'read-only' mirror of the repository,
that is only the recommended setup :). svnsync stores the metadata
that it needs in the revprops for rev 0 on the target repository. In
a failover situation, just set the revprops on the new target
manually, and put the triggers in place on the new source.
On 10/17/06, Thomas Harold <tgh@tgharold.com> wrote:
> Kyle Kline wrote:
> > All,
> >
> > 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.)
>
> Wouldn't DRBD or other high-availability software be a better fit?
> AFAIK, DBRD works at the block level, automatically transmitting
> disk-level updates from one server to the other.
>
> (DRBD is still on my to-do list for this month or next. We're running
> our SVN server inside a Xen guest and I need to get things setup so that
> I can move it between a pair of Xen servers.)
>
> ---------------------------------------------------------------------
> 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 Wed Oct 18 07:28:03 2006