开发者

SVN Mirror to become live REPO

开发者 https://www.devze.com 2023-02-04 08:47 出处:网络
I am creating a SVN replication process and have successfully created the mirrors using svnsync. I have been reading in the redbook and other posts and I\'m a bit confused. My question is, if my main

I am creating a SVN replication process and have successfully created the mirrors using svnsync. I have been reading in the redbook and other posts and I'm a bit confused. My question is, if my main server fails with my LIVE SVN Repo,开发者_StackOverflow中文版 what steps need to be taken to promote the Mirror to the LIVE repo? In this example I'm assuming my mirror is good and up to date.

is it? 1. modify permissions and users in authz and passwd 2. change UUID from backup servername to live servername


You should go ahead and make the UUID on the slave (backup) the same as the master (live) now. There's no point waiting until the master dies to figure you cannot do this.

To promote the slave to master, you'll need to remove the svnsync properties from the revision 0 on the slave repository. Check out the svnsync Bookkeeping section of this page in the Subversion book for an idea of what properties need to be removed. You may have to remove hooks scripts protecting the rev props to do this. This should be your first step.

Your second step would be to modify and synchronize (if need be) the users passwd and authz information.

If you have hook scripts on the master, you'll want to have backups on the slave and have script to get them applied quickly.

If you use an DNS name for you'll then want to point the DNS entry to the slave server instead of the master server. If you not connecting using a DNS entry now, you'll want to start getting everyone moved over sooner than later. Otherwise the next will be required for all clients who do not use the DNS name for the Subversion server connection.

Note: it may be required for some clients to perform a svn switch --relocate command on their working copies.

0

精彩评论

暂无评论...
验证码 换一张
取 消