When I try "svnadmin dump" on the old hardware I get the same error:
"DB_VERSION_MISMATCH: Database environment version mismatch"
So whatever upgraded the BDB to 4.3 on the new server has also done the
same on the old. Is there another way to upgrade the databases ?
The Subversion FAQ says:
Use this procedure to upgrade your repository in-place to Berkeley DB
4.3 or later:
Make sure no process is accessing the repository (stop Apache, svnserve,
restrict access via file:// <file://> , svnlook, svnadmin, etc.)
Using an older svnadmin binary (that is, linked to an older Berkeley
Recover the repository: 'svnadmin recover /path/to/repository'
Make a backup of the repository.
Delete all unused log files. You can see them by running 'svnadmin
Delete the shared-memory files. These are files in the repository's db/
directory, of the form __db.00*
The repository is now usable by Berkeley DB 4.3.
Where does one obtain an "older" svnadmin binary? How does one know if
it will be linked to the older Berkely DB?
From: Ryan Schmidt [mailto:email@example.com]
Sent: 26 August 2006 12:33
To: Kevin Turner
Cc: Subversion List
Subject: Re: Problems accessing repositories after migration to new
On Aug 26, 2006, at 13:19, Kevin Turner wrote:
> I have been using Subversion with Apache 2 on a Windows SBS 2003
> server for a couple of years without any issues. This week we
> migrated the operating system to a new server but I no longer seem to
> be able to access any of the repositories on the new server.
> I am using TortoiseSVN as a client. If I create new repositories on
> the server I can access them without any difficulty, so the
> installation is fine. However, if I try to access repositories that
> have been backed up and restored from the old server I get the
> "*PROPFIND request failed on <repository>. Could not open the
> requested SVN filesystem"
> Have I forgotten something that I need from the old server? I thought
> I would just need the repository folder.
When moving to a new server, moving the repository directory itself may
not be a good idea, especially if the repository is BDB-based, which it
probably is if it's a couple years old. You may now have a different
version of BDB which will cause problems. The Apache error log may say
something to that effect if you look.
I recommend you "svnadmin dump" the repository on the old hardware/ OS,
then "svnadmin create" a new empty repo on the new hardware/OS and then
"svnadmin load" the dump into the new repo. Use Subversion
1.3.2 or newer on the new server. Your new repo will be FSFS-based (not
BDB-based) so that in the future you'll be able to migrate to new
hardware simply by copying the repo folder as you expected.
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.6/427 - Release Date:
"NOTICE: The information in this electronic mail transmission is intended by CoralTree Systems Ltd for the use of the named individuals or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone, so that the sender's address records can be corrected."
Received on Sun Aug 27 14:04:34 2006