On 28/12/11 14:12, Daniel Shahaf wrote:
Jan Keirse wrote on Wed, Dec 28, 2011 at 11:44:49 +0100:
Hello,
I have a master and a slave. Now I want to discard the current master
and start using the slave as the new master (creating a new slave on
another server and stop the server that currently runs the master.)
I think the steps to do this are the following:
* Change authz on the master so that nobody can commit.
Either that or create a start-commit hook that always fails.
* Sync the slave one last time so it's certainly up-to-date.
(Shouldn't be necessary for us because this is done automatically in a
post-commit hook of the master.)
Also: disable revprop changes, and run 'svnsync copy-revprops' if needed.
* Remove the svn:sync-* properties from revision 0 of the slave.
* Change authz and hooks on the slave to what they used to be on the master.
* Have everyone relocate their working copies to the new server.
Either that, or change DNS.
If the master and slave repos have the same UUID and you change the DNS
your user will not have to do anything at all.
* Start syncing a new server so we have a slave just in case something
goes wrong on the master.
Is this correct? Is there something I forgot?
Looks good.
