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

Re: Upgrading to 1.3.2: "svnadmin: File already exists"

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-08-17 21:14:26 CEST

On 8/17/06, Jared Hardy <jaredhardy@gmail.com> wrote:

> Should I give up all these options now, in favor of hot-backup.py? Is
> there any way to recover from these dump errors?

There's no right or wrong answers here. It's all about tradeoffs and
making choices.

Yes, dumping your repository guarantees it's in a portable format.
But it's also equivalent to running 'svn checkout' on *every* revision
in the repository, so it takes a long, long time. Is the portable
output format worth all the extra time? Maybe so, maybe not.

When people ask me for best practices, I generally recommend:

* do a hotcopy once a week as your "full" backup. Very quick.
* do incremental backups every night by dumping only the latest revisions.
* do a portable full-backup once a month by dumping.

Adjust timings as necessary, based on the activity level of your
repository. It's all about finding a balance between portability and
speed. Portability is nice, but generally it's not something that
matters when you're trying to restore a backup after a crash.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 17 21:16:37 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.