On Wed, Feb 15, 2012 at 07:05:08PM +0000, Philip Martin wrote: > Stefan Sperling <s...@elego.de> writes: > > > But rather than going through that effort, I would recommend using > > svnadmin dump/load, or svnsync with file:// URLs, until Subversion 1.8 > > is released. At which point you can switch over to using > > "svnadmin hotcopy --incremental", which will copy rep-cache.db via > > the appropriate sqlite APIs. > > Are you suggesting this because you know the LVM snapshot method doesn't > work or just because it's a method that avoids non-standard Subversion > tools?
I don't know enough about SQlite to judge whether the DB will keep working at any frozen state a snapshot might create. And, yes, in general, using offical Subversion tools for backup purposes has the advantage that they will keep working after an upgrade. No matter what kinds of changes we make to repository fomats, we'll keep the official tools working. That said, I agree that filesystem snapshots should work fine, provided that sqlite databases will cope, too.
