Stefan Gehrig wrote:
>> Now, some folks *chose* to dump/load their repositories across the 1.4.0
>> upgrade because of the improvements to the backend storage system (better
>> compression == smaller disk footprint). You might decide to make the same
>> choice. But note that you needn't use an intermediate dumpfile in this
>> case. Simply install the new Subversion (1.4.5), and do the following:
>>
>> $ svnadmin create new-repos
>> $ svnadmin dump old-repos | svnadmin load new-repos --force-uuid
>>
> Exactly, Michael. We want to upgrade to also from Schema Version 3 to 5.
> I read the about the solution you propose, but in our case, it would take ages to upgrade!
> That's why I ask for another solution....
There's no need to go offline for a while dump/load process. My
recommendation would be to just upgrade to 1.4.5 and continue to use the
same repository. Additionally, create a new repository, and use 'svnsync'
to mirror your existing repository data into the new one. (See
http://svnbook.red-bean.com/en/1.4/svn.reposadmin.maint.html#svn.reposadmin.maint.replication)
Now, because your live repository will probably still be growing revisions,
you might need to run 'svnsync sync' a few more times. But eventually your
mirror repository will be basically "caught up with" your live one. At that
time, schedule a relatively short downtime window in which you can:
1) sync any remaining unsync'ed revisions to your mirror
2) run 'svnsync copy-revprops' to re-copy revision properties (see the
book for why this might be necessary)
3) swap out the repositories.
--
C. Michael Pilato <cmpilato@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Wed Sep 26 16:42:40 2007