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

Re: Size of hotbackup.py files versus svnadmin dump files

From: Michael <mixtim_at_ispwest.com>
Date: 2003-05-16 19:23:30 CEST

> Michael wrote:
> > Well, I've been running a modified hot-backup.py script for some time now
> > that has some features you might like. It performs a db_checkpoint on the
> > repo to make sure you aren't saving a bunch of logs you don't need and
> > then tar's and bzip's the directory and only saves those files.
> >
> > I only run it nightly from a cron job though as its a little cpu intensive
> > for a per-commit run.
> Yes could you please send me a copy?

Sure. Let me glance over it one more time (to make sure I'm not sending you
something bogus) and I'll send you a patch against the original hot-backup.py
> Anyone: what's the advantage in using hotbackup.py versus a straight
> svnadmin dump as a cronjob?

There is more to a repository than just your data. Backing up the entire
repo also saves your hook scripts and any unversioned items you store
with the repo. For example, I have a log-changes directory in my repo
where changes to unversioned items (such as log entries) are stored.
I also have several helper scripts in my hooks directory that change
from time to time.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 16 19:18:19 2003

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.