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

Re: Backup of repositories

From: Dave Neary <david_at_phenix.fr>
Date: 2004-09-28 09:41:45 CEST


dtandersen@cox.net wrote:
> What I do now is have a batch file run 'svnadmin dump' every night and
> copy the dump file over to the backup PC on the LAN. The dump file
> contains a perfect copy of the entire repository.
> svnadmin dump c:\svnrepos > yourfile.txt
> copy yourfile.txt \\somewhere\\folder


> I am curious to how other are doing backups.

It's an interesting question... our repository is on a partition which
contains a bunch of other stuff, and the entire partition gets backed up
regularly. But for really big repositories, it would probably be easier
to do incremental saves (you get the last backed-up revision, and dump
from that to HEAD only). I don't know if that's possible though, or
easily accomplished.

There are of course other ways to obtain the same result - by backing up
all of the berkley DB transaction logs before deleting them, you can (in
principle) rebuild an entire Berkley database without even having
subversion on there by replaying all the transactions. This also gives a
way to do an incremental back-up - you are only backing up the most
recent DB log files.

As suggested, you can dump & load the repository, or simply copy the
repository data (if you have your repository in /opt/svn then tar cfj
svn_backup.tar.bz2 /opt/svn will work). It's usually a good idea to
clean out your database logs regularly if you're diong this, since
otherwise you're basically doubling up the information you need.


David Neary
Phenix Engineering
110 ave Jean Jaures, 69007 Lyon
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 28 09:42:39 2004

This is an archived mail posted to the Subversion Users mailing list.