We have been using SVN at my workplace for a few years now and we really haven't done any kind of maintenance on it besides updates and backups since we installed it. Is there anything else we should be doing to maintain SVN or is what we've done all we really need to do?
+5
A:
See Repository Maintenance in the svnbook, especially the Cleanup section.
Marcus Lindblom
2009-04-30 11:49:54
I'll check it out. Thank you!
b_richardson
2009-04-30 12:18:50
how about accepting the answer? :)
Marcus Lindblom
2009-04-30 17:15:29
+2
A:
Subversion is basically maintenance-free if you are using FSFS on the back end. The BDB back end is a little touchier.
If you're using 1.6 (quite recent) on the server, you should consider doing a dump/reload and then running svnadmin pack to take advantage of server-side improvements in FSFS which make the repository more space-efficient.
bendin
2009-04-30 12:00:55
I was thinking, in particular of the last two paragraphs of this section: http://svnbook.red-bean.com/en/1.1/ch05.html#svn-ch-5-sect-1.3.1 when I wrote that.
bendin
2009-04-30 20:36:32
At work we run a SVN 1.2 server with several BDB repositories. Probably every 6 months, we have a BDB repository "lock up" which requires manual intervention to get that repository going again. No data loss, just a locked database transaction. Newer versions of SVN server should be able to self-recover in that scenario. We just haven't got around to upgrading yet.
Craig McQueen
2009-05-01 07:53:31