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

Re: the best migrate solution of lower downtime

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Sat, 9 Jul 2011 14:42:18 -0400

On Sat, Jul 9, 2011 at 12:54 PM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
> On 7/9/11 11:30 AM, Nico Kadel-Garcia wrote:
>> There are numerous others, such as pre-staging with "svnsync" to
>> switch arachitures or refactoring of projects into different
>> repositories, or finally getting things under $URL/project/trunk
>> instead of $URL/trunk/project.. In that case, the UUID's of the
>> repositories would be distinct, and switchover for clients is
>> trickier.
> You can use svnsync to do the copy, then change the uuid to match the old
> one as long as the final transaction matches - that is you do not do any
> commits during or after the last sync run.  It is much slower than rsync'ing
> the underlying files (and doesn't take hooks), but might be worth doing if
> the original repo started with an old version of subversion.

I've used that. It's potentially more dangerous, especially because
svnsync can be used with repository splitting.
Received on 2011-07-09 20:42:54 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.