You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ryan Schmidt <su...@ryandesign.com> on 2010/05/13 07:41:34 UTC

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

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?

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

Posted by Ryan Schmidt <su...@ryandesign.com>.
On May 14, 2010, at 12:17, Stonebraker wrote:

> svnadmin verify fails with this message "malformed representation
> header". From what i've read about it...
> " There is no fix without possible data loss.
> The only thing we could do is dump the repository till the repository
> is Ok then use
> svnadmin dump --incremental -r <bad rev +1>:HEAD
> You can examinie the broken revision with svnlook."

You should give fsfsverify a try.

http://svn.haxx.se/users/archive-2006-12/0786.shtml


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

Posted by Stonebraker <st...@gmail.com>.
Thanks for the response.  It sounds like it would be better to move
the corrupt repos to another *nix (instead of windows).

My new plan is to move the corrupt SVN 1.4.0 repos (on the FreeBSD 6.1-
RELEASE machine)via TAR + NFS to a Red Hat Linux 5.3 box (with SVN
1.4.0).

If I can get them there and hooked up in the same state they are in
now, that's good enough.

svnadmin verify fails with this message "malformed representation
header". From what i've read about it...
" There is no fix without possible data loss.
The only thing we could do is dump the repository till the repository
is Ok then use
svnadmin dump --incremental -r <bad rev +1>:HEAD
You can examinie the broken revision with svnlook."

any suggestions related to the tar + transfer between the freebsd and
red has linux box would be appreciated.


On May 13, 11:08 pm, Ryan Schmidt <su...@ryandesign.com>
wrote:
> On May 13, 2010, at 10:47, Bob Archer wrote:
>
> >> I would love to upgrade from version 1.4.0 (r21228) but a number of
> >> repos error out when I attempt to dump/svnhotcopy/svnsync I encounter
> >> errors.
>
> >> At this point we are just going to run a legacy 1.4.0 server (on my
> >> destination server) and the latest visual svn (and just start from
> >> scratch with all new repos).  My goal is to just move these old repos
> >> to the destination server by whatever means possible (and as of right
> >> now... the aforementioned commands aren't working).
>
> > Ouch. Have you tried to just upgrade your existing servers to 1.6.11? The newer version of dump or hotcopy or svnsync might work without upgrading the old repository. Of course you can upgrade it inplace using svnadmin upgrade. But, if that fails you will need to restore the repo... (I expect)
>
> > As far as just moving the repository folders from one to the other... I'd say give it a shot. Most of what I have read and heard is that will work if you are staying on the same OS and architecture but has problems if you try to move from one to the other... for example, Linux to Windows... not recommended without using dump/load.
>
> He already stated that he is moving from FreeBSD to Windows Server.
>
> I would strongly advise correcting the problems encountered by svnadmin verify before attempting to move the repository to a different server. The fact that svnadmin verify does not complete successfully is a pretty good indicator that the repository *is* corrupt at this point, and moving to a new machine will, at best, leave the repository as corrupt as it is now.

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

Posted by Ryan Schmidt <su...@ryandesign.com>.
On May 13, 2010, at 10:47, Bob Archer wrote:

>> I would love to upgrade from version 1.4.0 (r21228) but a number of
>> repos error out when I attempt to dump/svnhotcopy/svnsync I encounter
>> errors.
>> 
>> At this point we are just going to run a legacy 1.4.0 server (on my
>> destination server) and the latest visual svn (and just start from
>> scratch with all new repos).  My goal is to just move these old repos
>> to the destination server by whatever means possible (and as of right
>> now... the aforementioned commands aren't working).
> 
> Ouch. Have you tried to just upgrade your existing servers to 1.6.11? The newer version of dump or hotcopy or svnsync might work without upgrading the old repository. Of course you can upgrade it inplace using svnadmin upgrade. But, if that fails you will need to restore the repo... (I expect)
> 
> As far as just moving the repository folders from one to the other... I'd say give it a shot. Most of what I have read and heard is that will work if you are staying on the same OS and architecture but has problems if you try to move from one to the other... for example, Linux to Windows... not recommended without using dump/load.

He already stated that he is moving from FreeBSD to Windows Server.

I would strongly advise correcting the problems encountered by svnadmin verify before attempting to move the repository to a different server. The fact that svnadmin verify does not complete successfully is a pretty good indicator that the repository *is* corrupt at this point, and moving to a new machine will, at best, leave the repository as corrupt as it is now.


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

Posted by Bob Archer <Bo...@amsi.com>.
> >"Note that Subversion < 1.5 is not supported anymore. Please upgrade if
> possible. "
> I would love to upgrade from version 1.4.0 (r21228) but a number of
> repos error out when I attempt to dump/svnhotcopy/svnsync I encounter
> errors.
> 
> At this point we are just going to run a legacy 1.4.0 server (on my
> destination server) and the latest visual svn (and just start from
> scratch with all new repos).  My goal is to just move these old repos
> to the destination server by whatever means possible (and as of right
> now... the aforementioned commands aren't working).

Ouch. Have you tried to just upgrade your existing servers to 1.6.11? The newer version of dump or hotcopy or svnsync might work without upgrading the old repository. Of course you can upgrade it inplace using svnadmin upgrade. But, if that fails you will need to restore the repo... (I expect)

As far as just moving the repository folders from one to the other... I'd say give it a shot. Most of what I have read and heard is that will work if you are staying on the same OS and architecture but has problems if you try to move from one to the other... for example, Linux to Windows... not recommended without using dump/load.

BOb

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

Posted by Stonebraker <st...@gmail.com>.
Hi Ryan, I really appreciate your input on this, thank you.

> 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.

I would love to dump/hotcopy/svnsync these repos over but they all
encounter errors with those commands.  I'd prefer to just disallow all
connections to the repo, tar+lzop, transfer over to destination server
and hook it up to same version of svn.

I'm thinking that in theory this should work (as long as svn is
configured exactly the same on both servers)... I guess i'm just
looking for someone to say, "yeah that might work".

> Could you describe the error in more detail?
When I attempt to dump a 46 gb repo ...

# * Dumped revision 1703.
# * Dumped revision 1704.
# * Dumped revision 1705.
# svnadmin: Malformed representation header

svnhotcopy only copies about 6GB out of 46GB of the repo!


Svnsync fails after eight revisions ...

# ...
# Committed revision 8.
# Copied properties for revision 8.
# Committed revision 9.
# Copied properties for revision 9.
# svnsync: REPORT request failed on 'https://<url removed>'
# svnsync: REPORT of 'https://<url removed>': 200 OK (https://<url
removed>)

svnadmin verify also errors out

>"Note that Subversion < 1.5 is not supported anymore. Please upgrade if possible. "
I would love to upgrade from version 1.4.0 (r21228) but a number of
repos error out when I attempt to dump/svnhotcopy/svnsync I encounter
errors.

At this point we are just going to run a legacy 1.4.0 server (on my
destination server) and the latest visual svn (and just start from
scratch with all new repos).  My goal is to just move these old repos
to the destination server by whatever means possible (and as of right
now... the aforementioned commands aren't working).

thank you so much!

On May 13, 2:41 am, Ryan Schmidt <su...@ryandesign.com>
wrote:
> 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?