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.
