On 29/09/11 05:33, Rajesh wrote:
On Wed, Sep 21, 2011 at 5:59 AM, Daniel Shahaf<d...@daniel.shahaf.name> wrote:
Hyrum K Wright wrote on Wed, Sep 21, 2011 at 05:44:33 -0500:
2011/9/21 Ulrich Eckhardt<ulrich.eckha...@dominolaser.com>:
Am 21.09.2011 11:00, schrieb Hyrum K Wright:
[repository upgrade]
Since you are moving from 1.4 to 1.7, however, you may want to run
'svnadmin
upgrade' on the new repositories, to enable new features available
since 1.4.
Wait: I was under the impression that this enabled new features _as far as
possible_, but that some extensive internal changes (sharding? reverse
deltas? something?) actually required a dump/load cycle to make full use of,
or am I mistaken?
You're right: sharding may require a load to enable (though I seem to
recall a script somewhere would would do it to a live repo).
Things like packing can be enabled with a simple upgrade of the repository.
Except that sharding is a prerequisite to packing.
wanted to thank each and every one for their suggestions..
here is what i did.
1/ setup a new box with svn 1.7 rc3
2/ svnsync from main repo via a small script .. so all sync continues
on a cron schedule
3/ I have about 500 repos and 200G data so will take a month to sync ..
i observed that the packing is happening at the default 1000 rev into
its own dir and i decided to leave it at that .
4/ will do a dns flip and bring the 1.7 up and running.
5/ remove the 0 th property so no one can accidentally sync from the
previous location.
6/ make this new repo the master .. setup some other repository
browsing tools on the old location.
Thanks again for your time .. much appreciated help from each one of the folks.
Regards,
Raj
Don't forget to copy over your hooks as they are not copied by svnsync.
Also make sure to set the new repositories' UUIDs as the old ones or you
will have to do a switch --relocate on all your WCs
Giulio
