[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[RFE] support propagating changes from master to backup repository

From: Thomas Kühne <thomas-subversion_at_kuehne.cn>
Date: 2005-05-17 00:27:49 CEST

Two svn-servers hosting the same repository.
a) One server hosts the master and the other the backup/slave.
b) One server is part of a private network whereas the other is
connected to the internet and serves a public repository.

Keep those two servers in sync. Note that only the one server receives

current way:
1) dumping incrementals from the master repository
2) transferring the dumps to a local account on the slave repository
3) loading the incementals into the slave repository

proposed way:
svnadmin push master-url slave-url
The master sends updates to the slave.

svnadmin pull master-url slave-url
The slave requests updates from the master.

1) feature: Easy way to synchronize slave and master repository on
different servers with different availability.

2) security: Access to only one instead of two local accounts is
required for updating the slaves.

3) security: Compromise of one server/repository has no effect on the
other server/repository.

4) protocols: Pulling should be possible without a change of existing

5) protocols: Pushing requires transmissions of user/date-data that is
independent of the connection used for pushing.

6) db: Details(user, date, protocol infromation) should be logged for
each push/pull event in the slave repository.

Thomas Kühne

Received on Tue May 17 00:27:54 2005

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.