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

Re: best way to backup repositories

From: Rush Manbert <rush_at_manbert.com>
Date: Wed, 4 Jun 2008 09:49:51 -0700

On Jun 4, 2008, at 6:37 AM, Ulrich Eckhardt wrote:

> On Wednesday 04 June 2008, Marko Kaening wrote:
>> I wonder what the best way for a regular backup of svn repos is...
>> There is "svnhotcopy.py", but there is also the possibility of
>> "svnadmin
>> dump". The first would only work safely if there is no update of
>> the svn
>> version, but the latter might be a terrible slowdown of the backup
>> process
>> in contrast to simply copying the hotcopied svn repo dir.
>> Any hints for me?
> Use both. The hotcopy script is not much more than a simple
> filesystem copy,
> only that it copies things in an order that assures that you don't
> get an
> inconsistent repository if you are in the middle of a transaction.
> Then, from that repository, you create a dumpfile for which you make
> incremental backups using some backup software.

Why do this step? If I have the hot copy backup, doesn't that protect
me if my main repository is lost? Making a dumpfile and backing it up
incrementally seems to lose information that the hot copy preserved
(the configuration info), and I could always make a dumpfile from the
hot copy at the time I need to restore from it. But I would think I
would just replace the original repository with the hot copy if I ever
needed to do a restore after a disaster. Am I missing some subtlety
about the backup/restore mechanism?

- Rush

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-04 18:50:28 CEST

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.