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

Re: SVN backup with lvm snapshots and rsync

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 15 Feb 2012 19:05:08 +0000

Stefan Sperling <stsp_at_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

Running rsync on an LVM snapshot looks like it should work to me. An
LVM snapshot freezes the filesystem by diverting all writes into the
snapshot area. A Subversion repository in the frozen filesystem may
have transactions in progress, Subversion transactions or SQLite
transactions, but they won't change while the copy is made. If the
copied repository is ever used then these partial transactions will
simply be ignored. Provided Subversion gets its fsyncs and writes in
the correct order, and I believe it does, this looks like it should
work. I'd go as far as saying if the copied repository doesn't work
then this is a Subversion bug, or perhaps an LVM/OS bug.

Received on 2012-02-15 20:05:46 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.