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

Re: Backing up - is db/current written last?

From: Soren 'Frank' Munch <sm_sbv_at_u5.com>
Date: 2005-07-03 00:01:47 CEST

Daniel wrote:
> db/current is written last by svn.
> Also, fsfs is still transactional, so the commits are stored in the
> transaction directory until they are moved into place, and *then*
> db/current is updated.

Great! In that case db/current _must_ point to a set of valid file and there's
no reason to delay rsync.

> Thus, at worst, you will end up with a backup that does not include the
> last revision, *not* a corrupt repository.

I figured out this would be the worst case if db/current was not written last.

- - -

Well, the bottom line must be that grabbing the db/current first leads to
correct backups of the commit that wrote it. I assume is what hot-backup.py
is doing but I am one of those who would like to keep up an illusion that I
know what goes on and the raw "(s)cp db/current ..." and subsequent rsync is
very appealing.

Thanks for the information from the front-line!

Soren 'Frank'

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 3 03:07:35 2005

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.