[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: Greg Stein <gstein_at_lyra.org>
Date: 2002-07-18 20:08:04 CEST

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.

> Maybe the safe way to run hot-backup.py from post-commit is to
> background it with a 60 second sleep.

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).


Greg Stein, http://www.lyra.org/
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:06:32 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.