subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Schöning <tschoen...@am-soft.de>
Subject Re: epository UUID doesn't match after machine migration
Date Wed, 31 Oct 2012 08:57:00 GMT
Guten Tag Stefan Bauer,
am Mittwoch, 31. Oktober 2012 um 08:10 schrieben Sie:

> k1495kc@wcslin11g:~/comp/ost/db/customize> svn commit -m "generate 1
request with qty>>=1 instead of n containers" k1495kc_ost.pkb
> svn: Commit failed (details follow):
> svn: Repository UUID 'eb1e463c-bf85-11e1-bfe6-8716b2d39c66' doesn't match
> expected UUID 'd725acd1-4542-0410-9071-bb929a3732bb'

This is because with svnsync you need to create new repos which get
new UUIDs by default.

> I tried to set manually the UUID but without success:

> svnadmin setuuid control d725acd1-4542-0410-9071-bb929a3732bb 

> user(kcstd)@wcslin11g:~> svn up run
> svn: A reported revision is higher than the current repository HEAD
> revision.

I'm not sure but I think syncing between repos with the same UUID
won't work which would result in your new mirror repos got now more
new commits from some point, resulting in your working copy is to new
for the out-of-sync-repo.

> What is best practise to migrate a svn server to a new machines?

This depends on your environment and if the repos should be accessible
during the migration. If not and you used FSFS as repo backend, the
easiest way would have been to just copy the directories for each repo
to the new location, as this way you don't have to mind about
configuration, hooks etc. and UUIDs would have stayed the same. I did
this two weeks ago without any problems, even changing from 32 Bit
Windows to 64 Bit Ubuntu. Some of the core developers said that those
changes work in the current version of Subversion and with FSFS
backend without problems.

http://subversion.1072662.n5.nabble.com/Advice-on-migration-from-32-bit-platform-to-64-bit-td175066.html

Another way would have been a similar approach with creating new repos
as you did with svnsync, but afterwards dump the old repos and load
them into the newly created empty ones. This way the old contents and
UUIDs from the dump would get stored into the new repos. This way you
would have to copy configs and hooks over on your own.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


Mime
View raw message