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

Re: Problems After Repository Move

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Mon, 13 Jul 2009 11:33:57 -0500

On Jul 13, 2009, at 08:42, Richard Lichvar wrote:

> We recently moved a very large SVN repository from one Linux server
> to another (RHEL 5 to CentOS 5.3). I was told to just copy over the
> repository and the appropriate conf files. (Unfortunately there
> isn’t enough disk space on the old machine to export this multi-GB
> repository.) While the Kerberos authentication we do seems to work,
> we get a “no such revision” when trying to browse the repository.
> (This is from a local test repository on my local PC.) We are using
> variously TortoiseSVN and VisualSVN (the .NET developers using
> Visual Studio).
>
> 1. Is this a problem which can be fixed?
> 2. Or, do we actually have to export the repository on the
> old machine (probably to an NFS share we’ll have to have our IS
> department create) and then create the repository new on the new
> machine and import the repository? (In other words, can the
> repository and conf files be copied over as suggested and perhaps
> in the copy process did something screw-up? We did have a couple of
> cases where revs didn’t want to copy; but after multiple re-trys
> they did. The revs in question happened to be 1+ GB each.)
>

When moving repositories between machines running different OSes, you
should probably use svnadmin dump and load, and not move the
repository files directly. The dump will not include conf files or
hook scripts, though, so you will have to copy those manually later.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2370984

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-13 18:36:02 CEST

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.