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

Re: Moving Repositories to New server

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 26 Jul 2011 17:08:38 +0200

On Tue, Jul 26, 2011 at 10:35:02AM -0400, Phil Pinkerton wrote:
> Are there any know issues with regards to moving Repositories from one
> platform to another ?
> Will the old Repositories maintain their current SVN revision ?
> Current platform Sun Solaris 10: SVN 1.6.5
> Target platform Red Hat Enterprise 5 SVN 1.6.17 ( Subversion Edge )
> Planned steps (Creating a script for the dumps and loads as there as a
> few hundred Repositories to move.)
> (1) Freeze the repository . Take a dump of the repository.
> (2) Verify the file is dumped correctly by making sure that the last
> version dumped is the same as the one in the live repository. Also
> check the return code of the svnadmin dump command.
> (3) Copy the dump file over to the new server. Verify that the file is
> copied over correctly.
> (4) Load the dump
> (5) Verify the load.

If your repositories are in FSFS format (check the file "db/fs-type")
you don't need to perform a dump/load cycle. It doesn't hurt,
but it can take longer than copying the repositories directly.

Run 'svnadmin verify' on all repositories before you start moving them.
If all is good, disable commit, and run 'svnadmin verify' again for
revisions you didn't have in the previous run (see the -r option).
Then use 'svnadmin hotcopy' to copy the repository to a disk,
transfer it to the new server, run 'svnadmin verify' on it again,
and enable commit at the new location.

> (6) Migrate and hook scripts or authorization files over.

'svnadmin hotcopy' will copy all files in a repository (except
versions prior to 1.6.11 which do not copy db/conf/fsfs.conf
because of a bug).

> (7) Verify the scripts and configuration files work.
> (8) If you have a name for the server for accessing it. You might have
> to point the name to the new server.
> a. use switch ?
> b. or relocate ?

You need relocate (on the 1.6.x command line, this is confusingly
called 'svn switch --relocate') if the hostname or the access protocol
(http://, svn:// etc.) of your new server is not the same as the old one.
Received on 2011-07-26 17:09:17 CEST

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.