Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type;
  b=eY4JQv2miO+PjpY/VqthwnRvPCwzw24Q9a0Sd21fM6BURVj98zG8pibfgszqOyo9IyqYqE2NvkL0+XXX1gSt8yz6+SgnS/+dQImSsSREKVW1ZWv6YKQDl9dNFK0fFv/y9olKyC0r7v6FrXZXMSvB+Wh6i/k8xT78qY167UsnOmU=;
Message-ID: 
 <1362766488.28855.BPMail_high_carrier@web121101.mail.ne1.yahoo.com>
Date: Fri, 8 Mar 2013 10:14:48 -0800 (PST)
From: carol schaef <carol.schaef@yahoo.com>
Subject: VisualSVN on clustered windows server 2008
To: Users@subversion.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


I would like to run VisualSVN Server vs 2.5.8 in a clustered windows server 2008 environment. The configuration would be, VisualSVN installed locally on the c drive and the repository installed on a cluster shared volume (csv). VisualSVN presents 2 paths during installation to separate these. Upon failover VisualSVN would be accessible on another node, continuing to use the csv as the repository. Upon failover we would also like not to change the url which references svn in a Development environment. Would "https://[ipaddress of the cluster]:port/other directories" work in accessing the repository? We would also like to use VisualSVN's web interface and would like the web address not to change after failover.

On Microsoft's technet website they discuss cluster-aware application requirements including, The application must use an IP-based protocol, The application must be able to specify where the application data is stored and client applications that connect to the server application must retry and recover from temporary network failures. On the third item, typically that would be eclipse as a client.

Any responses regarding whether this configuration is possible would be helpful.

Tia, carol