Unlike 'svnadmin dump', hotcopy will happily back up a corrupt revision and not tell you. It's really just a clever filesystem backup with a very careful time ordering of certain key files in case there is a transaction in progress when it runs. Having been bitten by this myself[*], we now run svnadmin out of cron every night before we run our hotcopy. We also keep a week's worth of hotcopies, and I check my cron emails every morning.
Tony. [*] fsfsverify.py is your friend -----Original Message----- From: Neil Bird [mailto:n...@jibbyjobby.co.uk] Sent: 16 September 2011 09:54 To: users@subversion.apache.org Subject: Re: How to fix corrupt revision in repo? Around about 15/09/11 03:30, David Hopkins typed ... > I have an SVN repo that is failing svnadmin verify on revision 192. Slightly OT, if I may: would a 'svnadmin hotcopy' also show up errors that 'verify' would? We use hotcopy to pull our repos off the SVN server onto a backup-up network drive, but we don't use verify regularly. The network drive has incremental backups so if we see an error during the copy we can still get older, valid, copies of revs. back. Do we need to be running verify as well? -- [neil@fnx ~]# rm -f .signature [neil@fnx ~]# ls -l .signature ls: .signature: No such file or directory [neil@fnx ~]# exit ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ----- No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1410 / Virus Database: 1520/3899 - Release Date: 09/15/11 ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
