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

Re: move a repository to a new machine (from a dead one)

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Tue, 2 Jun 2009 15:00:07 -0500

On Jun 2, 2009, at 10:29, Syd Bauman wrote:

> I had a lovely Subversion server running on Debian GNU/Linux on a
> PowerPC machine in my basement. It only used the SVN protocol, but I
> was happy as a clam.

> So I got a different box (an AMD i386 architecture machine),

> * copied the Subversion repositories from the backup of the old

> And ... well, it half works. I can talk to Subversion from the
> various machines with clients and working directories -- I can issue
> `svn stat -u` and can check out new copies. But trying to commit
> changes results in the error message "Cannot negotiate authentication
> mechanism". I tried erasing the ~/.subversion/ directory on a client

The usual wisdom is that if your old server and new server use the
same architecture, same major OS version, same version of APR and
Subversion, you can just copy the repository, but for anything more
complicated, a dump and load is recommended. With a BDB repository,
copying the repository to a different architecture shouldn't work at
all, I believe. So the fact that yours is slightly working means you
have an FSFS repository. I'm not sure if the issues you're seeing are
due to such issues, but if possible, try to find a machine with the
same specs as the one that died, put the repository on it, and run
svnadmin dump on it. Then try to load that dumpfile into a new
repository created on your new server.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-02 22:01:12 CEST

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