RE: Subversion 1.4.6 -> 1.5.2 migration - sanity check please
From: Sholokhov, Vitaliy <vsholokhov_at_marvel.com>
Date: Fri, 26 Sep 2008 09:35:34 -0400
We've installed subversion 1.5 server on top of 1.4.6 without any
There's no reason to do such heavy lifting with migration. It all works
P.S. Backups never hurt anyone in any case scenario ;-)
________________________________
From: David Aldrich [mailto:David.Aldrich_at_EU.NEC.COM]
Hi
We are planning to upgrade our svn server from 1.4.6 to 1.5.2. We are
We have multiple repositories (one for each of our projects) in FSFS
The plan is:
1) Install svn 1.5.2 onto new server hardware, running under Centos 5.0
2) Notify users and disable access to 1.4.6 server
3) Backup each repository using 'svnadmin dump' (or could use tar - I)
4) Run both svnadmin upgrade and svn-populate-node-origins-index on each
5) Map existing http: url to point to new server
6) Notify users that new server is up and running.
Users will remain at 1.4.6 client for now. I see no reason for them to
Some file locks may be active, do we need to look after those in some
Anything else we've forgotten?
Best regards
David
******************************************************************************
|
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.