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

Re: Problems accessing repositories after migration to new server

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-26 13:33:04 CEST

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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 26 13:34:08 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.