Multiple sites....in a way again: Replication ;)

[aluetjen]

Hi there!

More and more we have the need to maintain source in multiple sites. Even worse, those sites are pretty far away causing considerable latency to source control operations (500ms delay by network and as it really has pretty high latency out of VS IDE anyway it gets really worse). I know that SQL replication is a hard thing to do and wont even fix the problems and we wouldn't be able run transaction based replication which is required to keep consistancy.

However something like a "multi homed" repository would be a fancy feature.

Lets say:

* It would be possible to have multiple database in something like a site structure.
* A folder in a repository has something like a "Primary Site"
* Changes in that folder can only be made to the server at the primary site.
* Secondary sites are readonly which means that changes initiated at a secondary site are simply proxied to the primary site.
* Changes can be one-way synchronized from primary site to secondary sites

In a scenario where one has a central build server and source control but mutiple sites working on dedicated projects that would help a lot and maybe is much easier to implement.

Do you consider implementing features in this direction for enterprise environments?

Best regards, Alex

[lbauer]

We have had several requests from users who want to replicate or back up the database to a remote location. I'ts been logged as a feature request. Right now Vault does not support database replication. I'll add your "vote" and also add your multiple site description.

We'll take a look at this plus other ideas for helping users with their need to have copies of the database at more than one location.

[MikeFischer]

You can add me as another Vote for replication or some other distributed environment method.