Re: upgrade to 1.6.2 and working copies

Beatriz Stratton wrote:
>[...]
>We are planning to upgrade our Subversion repositories to
>1.6.2 (from1.4.3).
>[...]
>2. svnsync + switch over afterwards [...]
>3. svnadmin dump + svnadmin load - [..]

If you want to minimise the downtime, you will need a 2 step approach.

1) With either methode create a mirror of your repo in the same
parent directory (make sure the uuid of the new repo matches the old,
otherwise you will have to recheckout your WCs).

when the new repo is ready (if there is much commit traffic, you won't
get it up to par without taking the repo offline).

Make sure all access control, hooks, ... are in place.

2) Now take the repo offline.

Catch up with the latest commits (incemental dump+load, or running
svnsync again).

Rename the old repo or move it out ouf the way, then give the new repo
the old name.

Restart the server.

Done!

I don't think either dump/load nor svnsync will preserve locks.

-- 
Lorenz
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2359291
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].