1

We are using SVN and we have on-site and off-shore teams. SVN repository is currently in on-shore premises which means that connectivity from off-shore to SVN is very slow. We would like to setup and SVN at off-shore too. We would require the two SVN repositories to be in-sync. What would be the best practice to do this, any third-party product required?

Thanks!

bahrep
  • 29,961
  • 12
  • 103
  • 150
user1340582
  • 19,151
  • 35
  • 115
  • 171

3 Answers3

3

Here you will need to setup an SVN master-slave setup.

Basically:

  • The slave server has his own local repository and can serve local read requests
  • Write requests to the slave server have to get forwarded to the master server (using WebDAV proxy or post-commit hooks, I would go with the second one)
  • The slave repository has to be synchronised with the server's repository (using svnsync)

This blog post is a good starting point if you prefer to use WebDAV, while this post will show you how to setup a synchronisation using post-commit hooks.

Note that you will also have to modify the default pre-revprop-change hook script on your slave server as svnsync will need to modify some properties directly.

Community
  • 1
  • 1
Yannick Blondeau
  • 9,465
  • 8
  • 52
  • 74
  • 1
    It's called 'write-through proxy' and is described in http://svnbook.red-bean.com/en/1.7/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.writethruproxy BTW do you intentionally provide links to outdated SVNBook? :) – bahrep Aug 30 '12 at 07:40
  • Sorry for the links to the old version of the SVNBook, I've edited the URLs. Seems that I will have to update my bookmarks :) The content (on these pages) remains quite the same though... – Yannick Blondeau Aug 30 '12 at 07:44
  • I read the link at svnbook.read-bean.com/en/1.7/. Good stuff. I forgot to mention that we use 'svnserve' and there seems to be some limitations regarding it. I also didn't quite understand whether svnsync locks a read operation from a slave until the write operation to master has been fully synced to the slave. – user1340582 Aug 30 '12 at 13:30
  • 1
    That's the best non-commercial option, but you have to bear in mind that only the master is writeable (so can be a single point of failure) and if the slave gets out of sync you'll end up with multiple conflicts. – Mand Beckett Aug 31 '12 at 11:07
1

Since you asked about third party products, WANdisco Subversion MultiSite is a third party product that uses true active-active replication to provide seamless HADR and global multi-site for Subversion repositories. Writes and reads are always to the local, LAN repo. Our customers come to us from svnsync deployments as described above because they want performance, scalability, and data safety beyond that svnsync supplies.

DVCS does not fix the WAN clone or replication issue on its own.

Disclaimer: I am an employee of WANdisco plc

James Creasy
  • 653
  • 1
  • 4
  • 15
0

VisualSVN Server 3.0 (Enterprise Edition) introduces Multisite Repository Replication feature which follows classic master/slave replication architecture. The feature is based on VDFS (VisualSVN Distributed File System) technology that allows bidirectional, automatic and transparent replication of data between multiple remote sites:

  • Both slave and master repositories are writable and act like a regular Subversion repository from the enduser's standpoint.

  • Works out-of-the-box. You are only required to perform minimal permission management for repository replication and adjust firewall rules,

  • Replication is done automatically and transparently.

See "Getting started with Multisite Repository Replication".

bahrep
  • 29,961
  • 12
  • 103
  • 150