Phil Pinkerton <pcpinkerton_at_gmail.com> wrote on 07/26/2011 09:35:02 AM:
> 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.
>
> (6) Migrate and hook scripts or authorization files over.
>
> (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 ?
>
>
> (9) Unfreeze the repository.
As others have stated there are multiple ways. Be careful if your users
use file locking, since most of the options will ignore lock tokens.
(Just as most of the options ignore hook scripts and authorization files.)
I've gone from Red Hat 3 to Solaris 10 (both x64) by just rsyncing the
fsfs filesystem. (It is best to ignore transactions and sync the current
file first if you plan on doing the initial rsync with a live database.)
I've gone from Win 2003 x86 to Win 2008 x64 by svnsync.
I've gone from Solaris to Windows using dumpfiles.
I've gone from Windows to Red Hat with svnsync.
I've played with hot copies, but not used them for much.
They all have worked. Dumpfiles are by far the slowest and will
take considerable temporary space if you have repositories of any
significant size. However, I would consider dumpfiles the safest
since you essentially will have a complete separate portable copy
of the whole repository. (minus locks, hooks, and auth stuff
mentioned above.)
svnsync can also be quite slow, but would probably require less
downtime since you can sync and re-sync live repositories.
(Just make sure you either have rev-prop changing disabled or
have a way to identify already sync'd rev-prop changes.)
Kevin R.
Received on 2011-07-26 19:04:42 CEST