Re: High Availability Recommendation
From: Johnathan Gifford <jgifford_at_wernervas.com>
Date: 2007-01-29 22:04:36 CET
For a failover setup like the one you mention below, if Apache's IP address and port it is serving on doesn't respond, then failover. Since your using Apache as your access method to Subversion, Subversion itself is not affected by communication issues. You may want to install the Subversion binaries on the NFS mount though.
I'm not a Solaris expert, but you may be able to have both servers NFS mount the repository drive at the same time and the Apache instances on both servers running at the same time. If you have a load balancer, you could utilize both servers at the same time. That way all resources are always active instead of one waiting to take over. There were some issues with NFS in versions earlier than Subversion 1.3.x, but that may have been taken care of now if you use the FSFS repository format (which is default).
For your DR site. Consider using the svnsync feature from Subversion 1.4.x. This will create a mirror that is synchronized immediately with your primary site server. In the event of a disaster, you'll only need to modify revision 0 of each repository mirrored to make it writable on the server at the DR site.
Johnathan
>>> On Mon, Jan 29, 2007 at 2:48 PM, in message
---------------------------------------------------------------------
|
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.