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

Re: post-commit & hot-backup.py

From: Blair Zajac <blair_at_orcaware.com>
Date: 2002-07-18 20:31:06 CEST

Greg Stein wrote:
> On Wed, Jul 17, 2002 at 10:42:26PM -0700, Blair Zajac wrote:
> > How does svn.collab.net run hot-backup.py? Via cron?
> post-commit hook, as mentioned elsewhere.
> >...
> > Is the repository modified at any point after post-commit is called?
> It sure could be. Any time that somebody does "svn update", the database
> will get modified (cuz a txn is constructed to mirror the WC). I imagine
> something like "svn diff" would also do it, as the server constructs a txn
> for that, too.

OK, thanks. I meant for that specific commit, the database is not
modified at all once post-commit is run. Obviously, if I put on my
thinking hat, then the post-commit script gets a revision number
which implies that the transaction has completed. Dah..

> Changes will *always* be occurring. There is no way to "wait" for an
> unchanging database. Thus, you must always use the recommended BDB backup
> procedure: copy out the files *then* copy the log files. This is what
> hot_backup does, along with trimming log files.
> Note that some people may not want to trim log files, however, as that
> removes the ability to "replay" all transactions from epoch until the
> current point in time (e.g. if you want to reconstruct the db as it was at
> an arbitrary point in time).

I guess, if you were concerned about disk space and still wanted all the
log files, then you could run hot-backup.py and never delete old backups
or snapshots. You could then always put together the log files from
revision N (where N is the revision of your first hot-backup.py) to
M by picking the latest saved log.XXXXX for each XXXX. This would save
disk space but be a hassle to pick the latest log.XXXXX files when you
had to do a recover.


Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 18 20:32:04 2002

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.