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

Re: Problems with the Migration of a old repository to a new Subversion and BerkeleyDB Version

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2005-12-22 12:54:03 CET

On Dec 22, 2005, at 11:44, Richard Musil wrote:

> Gasser Rolf RUAG E wrote:
>
>> I installed the new subversion 1.2.3 with the BerkleyDB 4.3 on our
>> Linux
>> Server.
>> All seems to be ok, if I work with new repositories.
>> But if I try to migrate our old repository based on Subversion
>> 1.0.6 on
>> a BerkleyDB 4.0.24 to this new version, I'm not able to
>> work with this repository on the new environment.It is not
>> readable.(I
>> cannot see the repository with a ordinary browser and cannot
>> checkin/checkout)
>> I found a workaround on the tigris.org FAQ to delete all old
>> dblogs and
>> shared memory files after upgrading to Berkeley DB 4.3, but this
>> workaround is not working.
>
> Did you just copy the repository over, or did you 'svnadmin dump',
> 'svnadmin load' cycle? If the former was the case, I would suggest
> trying the latter.

This is also an excellent opportunity to get off of BDB and onto
FSFS. svnadmin create will, by default, as of Subversion 1.2.0,
create FSFS repositories, not BDB repositories, which IMHO will cause
you less grief in the future. Run svnadmin dump on the old server,
bring the dumpfile over to the new server, run svnadmin create and
svnadmin load, and you're done.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 25 04:37:49 2005

This is an archived mail posted to the Subversion Users mailing list.