SVN repositorires migration using svnsync and master information in repos.

[Ravi Roy <ra...@gmail.com>]

Hi,

I'm in process of migrating my repos from 'master host'  to larger
disk to resolve the space issues on a 'new master host'. I have
compiled and installed Subversion 1.6.18, Apache 2.23 on CentOS 5.9 in
a new Virtual Machine (as 'new master host'). I have migrated all
repositories using 'svnsync' from 'master host' to this 'new master
host'.

'master host' has Subversion 1.6.1.

I have verified that all repos on 'new master host' has same revision
numbers for corresponding repos as on 'master host' . Is that
guarantees that databases for all repos are migrated successfully to
'new master host' ?

Secondly, since 'master host' does not have any master information
under '/usr/share/repos/Repo-A/db/revprops/0/0' but 'new master host'
has master info under 'usr/share/repos/Repo-A/db/revprops/0/0', since
'svnsync' have been used for repos migration.

 -- Do I need remove this master information from
'usr/share/repos/Repo-A/db/revprops/0/0' on 'new master host' or it
does not harm being it a new master subversion server ?

Thanks you!

Regards

Ravi.

Re: SVN repositorires migration using svnsync and master information in repos.

[Ravi Roy <ra...@gmail.com>]

> am Samstag, 30. März 2013 um 09:59 schrieben Sie:
> No, there was a similar discussion recently:
>
> http://mail-archives.apache.org/mod_mbox/subversion-users/201303.mbox/%3c21DA556C6089D34FB2D99CC5FB0422C306BB18EC@lux-mail2.luxembourg.intrasoft-intl.private%3e

Thanks Thorsten for the reply and pointing me to thread. I will cross
check the stuff with respect to this.

>
> svnsync will create each revision from your master even if it is not
> allowed to read actual data because of path based access restrictions
> on the master or simply because you provided a wrong root path on
> initializing the repo for syncing. You need to compare repo contents,
> e.g. using a client and some svn ls operations or dumping your soiurce
> and target repos and comparing their sizes or something similar.

I had disabled patch based restrictions before migration of repos and
also made sure that root path for source and target is correct.
Have to check the size of the repos.

> I think it doesn't harm and is easily removable by svnadmin, but
> others will know for sure. Besides that, more important to consider is
> that your new repos should have got new UUID each, meaning they are
> incompatible with your current working copies now. Each working copy
> needs to be checked out again, svn relocate doenst work because of the
> new UUIDs, you didn't just moved your repos but created new ones, or
> you have to manually set the new reop's UUID to the old ones using
> svnadmin setuuid. In the latter case you have to make sure that both
> repos do have exactly the same content, meaning now revisions
> committed after syncing etc.

Every new repository on 'new master host' was created using UUID from
old repos. so all repos on 'master host' and 'new master host' have
same UUIDs.

I will verify the contents of repos...thanks again..

Thanks.

Ravi.

Re: SVN repositorires migration using svnsync and master information in repos.

[Thorsten Schöning <ts...@am-soft.de>]

Guten Tag Ravi Roy,
am Samstag, 30. März 2013 um 09:59 schrieben Sie:

> I have verified that all repos on 'new master host' has same revision
> numbers for corresponding repos as on 'master host' . Is that
> guarantees that databases for all repos are migrated successfully to
> 'new master host' ?

No, there was a similar discussion recently:

http://mail-archives.apache.org/mod_mbox/subversion-users/201303.mbox/%3c21DA556C6089D34FB2D99CC5FB0422C306BB18EC@lux-mail2.luxembourg.intrasoft-intl.private%3e

svnsync will create each revision from your master even if it is not
allowed to read actual data because of path based access restrictions
on the master or simply because you provided a wrong root path on
initializing the repo for syncing. You need to compare repo contents,
e.g. using a client and some svn ls operations or dumping your soiurce
and target repos and comparing their sizes or something similar.

>  -- Do I need remove this master information from
> 'usr/share/repos/Repo-A/db/revprops/0/0' on 'new master host' or it
> does not harm being it a new master subversion server ?

I think it doesn't harm and is easily removable by svnadmin, but
others will know for sure. Besides that, more important to consider is
that your new repos should have got new UUID each, meaning they are
incompatible with your current working copies now. Each working copy
needs to be checked out again, svn relocate doenst work because of the
new UUIDs, you didn't just moved your repos but created new ones, or
you have to manually set the new reop's UUID to the old ones using
svnadmin setuuid. In the latter case you have to make sure that both
repos do have exactly the same content, meaning now revisions
committed after syncing etc.

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

Re: SVN repositorires migration using svnsync and master information in repos.

[Daniel Shahaf <da...@elego.de>]

Ravi Roy wrote on Sat, Mar 30, 2013 at 14:29:06 +0530:
>  -- Do I need remove this master information from
> 'usr/share/repos/Repo-A/db/revprops/0/0' on 'new master host' or it
> does not harm being it a new master subversion server ?

Don't edit files under the db/ dir (other than fsfs.conf) by hand.  In
this case you should use 'svnadmin setrevprop' or 'svn propedit'
instead.