[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: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 13 Jan 2009 10:24:45 -0500

On Tue, Jan 13, 2009 at 10:19, James Green <James.Green_at_occam-dm.com> wrote:
>> Better to follow this procedure.
>> http://svnbook.red-bean.com/en/1.5/svn.reposadmin.maint.html#s
>> vn.reposadmin.maint.migrate
> Hi Andy,
> Thanks for the email.
> I've just had a read through this link and I'm not sure what I would
> gain by going through this process. Why would you prefer this method
> over a plain copy?

It's much safer and eliminates any chance of corruption due to library
& architecture differences. If you're upgrading from an older version
you can more easily take advantage of newer features (better diff for
storage, better compression, etc.).

> I did a test on a small Repository copy. I then Relocated my working
> copy to point to the new server and all was well, all the history
> (revision data) was present and correct in the new version.

If you're using FSFS AND moving to the same or newer SVN version AND
no one is accessing the repository while you're doing the copy (or you
use hotcopy) AND moving to the same OS & CPU architecture, then yes,
this process will probably be OK.

But a dump/load cycle will ALWAYS work out properly.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-13 16:25:39 CET

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.