[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-18 04:41:35 CEST

On 8/17/06, Sigfred Håversen <bsdlist@mumak.com> wrote:

> Any backup scheme that does not use 'svnadmin dump' for long term storage is
> _very flawed_. To put words into your mouth (sorry): any implicit of not using
> 'svnadmin dump' runs _very_ contrary to what was adviced before 1.x, speaking
> as a user since about 0.32. Please correct me if I am mistaken in this so
> that I may change my backup strategies.

See my email about backup best practices. I recommend an occasional
dump for long-term storage, but hotcopy for everyday backups.

The only reason we recommended dumping on every release before 1.0 is
because we were changing the db schema on nearly every release! It
was *required* to upgrade. Now that 1.0 has been released, we've made
a promise that no dump/load cycle is ever required to upgrade... until
we reach 2.0.

> As of 'svnadmin dump' is slow: I thought that relability and integrity of the
> repository is what is important.

It's not the only important thing, it's one of many important things.
If the disk crashes and you have to restore from backup, would you
rather tell your users to wait 10 hours for a dumpfile to load, or
wait 3 minutes for a hotcopy to be restored? Downtime matters too.
Mix the strategies.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 18 04:42:00 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.