----- Original Message -----
From: "Ulrich Eckhardt" <firstname.lastname@example.org>
Sent: Wednesday, July 19, 2006 5:02 AM
Subject: Re: Migrating Multiple SVN Repositories to new server
> On Tuesday 18 July 2006 23:11, Santhosh Raghunath wrote:
>> We would like to know the detailed steps involved in migrating the
>> multiple SVN repositories residing on the current box to the new box. I
>> have read about the 'svnadmin dump' and 'svnadmin load' commands. But I
>> am not sure if this has to be run for each repository (around 7-8 in our
>> case) separately? Is there any other simpler and sure shot way.
> 1. dump and load only transfers the repository content, you would still
> to convert/copy the other setups like permissions or hooks.
> 2. If the target machine is sufficiently similar to the source machine,
> copying the files that make up the repository will work. Be careful though
> that you don't change permissions doing so in an inappropriate way, see
> book for further info. 'sufficiently similar' means in the case of BDB
> the used BDB libs are also of the same major and minor version and that
> computer is running the same OS on the same type of hardware. The FSFS
> doesn't need such precautions, which is why it is favored as easier to
> 3. You can run a dump before and after migration and compare them to make
> both are still the same.
And make damn sure you've got clean backups *before* and immediately *after*
In fact, strongly consider this as a good time to do cleanups: making sure
that you do a "svn switch" for clients and have a new hostname for the new
server will help you enforce this. And this is a good time to switch to
Also, consider using "hot-backup.py" in order to get all the hook scripts
and permission files, and to make clean backups before the move.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jul 19 11:55:07 2006