It worked! Thanks a bunch! As you suggested, I needed to run 'svnadmin recover' to all repositories, since before that I got some error msgs for version incompatibility. After that I could do both checkout and 'svnadmin dump' locally on command line. Also, I verified that I could commit all the changes to a repository to a fresh empty repostory using one of the dumpfiles.
Thanks a lot!!!!!
From Ulrich Eckhardt <firstname.lastname@example.org>
Sent Mon 9/10/2007 5:01 PM
Subject Re: Disaster recovery: simplest way re-create our svn on another Linux server, for dummies
Okay, let's see what we can do...
0. Make a backup. Some of the things here require writing the repository. You
will also need write access, even just listing the content needs it because
of lockfiles that need to be created. You don't have to be root (and
1. Try to see if the locally installed Subversion can read the repository.
Typically, you would just do 'svn log file:///path/to/repos' and if you get
the log, the BDB is readable with the current client and you can simply dump
2. If that doesn't work, you might be able to upgrade the BDB database using
db_recover (or 'svn recover'?) and then try again.
3. If all this doesn't work, you will need an old environment where it can be
read. I'd suggest that you install Debian in a virtual machine or directly
retrieve the binary packages and fumble together a working and usable SVN
installation, but that is not really trivial. If this still fails, it is
probably due to the fact that the current machine is simply a different
hardware architecture, e.g. you can't move a BDB between a 32 and 64 bit
architecture or between a big and little endian machine.
> If possible, I'd love to skip the installation and configuration of
> apache2, and just do locally an 'svn checkout' and 'svnadin dump' in
> the simplest way possible, on Linux command line.
Apache only plugs an HTTP-based service and access control on top of the
direct access, you don't need it. ;)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Sep 11 13:48:30 2007