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

Re: SVN Migration using tar only, is this possible (without dump or hotcopy)?

From: Ryan Schmidt <subversion-2010b_at_ryandesign.com>
Date: Thu, 13 May 2010 02:41:34 -0500

On May 13, 2010, at 02:35, Stonebraker wrote:

> I need to move a few very large repositories (one over 30 GB) to
> another server (both servers use SVN 1.4.0.)

Note that Subversion < 1.5 is not supported anymore. Please upgrade if possible.

> Server 1: FreeBSD 6.0
> Server 2: Windows Server 2003 x64
> Transfer method: NFS (Network File Share)
>
> Are there any issues with just tarring up the repositories and
> transferring them over NFS to my destination server (assuming no one
> commits anything) then doing a setuuid and moving over the user
> database?
>
> Will this scenario work?
> 1. Tar repository (assume there are no commits during tar)
> 2. Transfer .tar to destination server
> 3. untar
> 4. transfer svn user database to destination (modify config files so
> svn knows path)
> 5. setuuid on repo

Probably not recommended. Repositories are not meant to be portable, but dumpfiles are. Though note dumpfiles do not include anything other than the revisions. In particular dumpfiles do not include hook scripts or configuration files; these must be transferred separately.

> Note: I am unable to use svnadmin dump or hotcopy (both error out..
> which is why i'd like to pursue this).

Could you describe the error in more detail?

Have you already run "svnadmin verify"? Does it succeed without error?
Received on 2010-05-13 09:42:14 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.