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

Upgrading Subversion

From: Brian Brophy <brianmbrophy_at_gmail.com>
Date: Thu, 26 Feb 2009 06:59:28 -0500

We have a larger repository (62 GB with over 125,000 revisions) that is
currently running 1.3.2. We're planning to upgrade this summer. With
1.6 on the horizon, would it be recommended to wait until a 1.6.x
release and upgrade then, or upgrade to 1.5.5 sometime before then? We
will probably only do one upgrade this year.

Also, considering the size of our repository, what is the recommended
upgrade approach?
1) svnadmin dump the full repository. upgrade the SVN binaries,
including mod_dav_svn Apache modules. svnadmin load the dump.
2) upgrade the SVN binaries, including mod_dav_svn Apache modules.
svnadmin upgrade the repo. run the svn-populate-node-origins-index program.
3) other?

For consideration, our backup scheme includes nightly svnadmin hotcopy
runs to a unique folder (2 previous ones kept), file system backup using
a traditional backup program, as well as the incremental dumps of every
commit performed using a post-commit script (kept for 30 days).



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-26 13:00:15 CET

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.