Hot backup changes

I'm considering making the following changes to the hot backup
scripts to have much smaller backups. Right now our repos/*
directories sums to 12 Mbytes, but our recent hot-backup.py
directories each take 10-20 Mbytes. All the hot backups for
the 100 revisions we have use 1 GByte. The is excessive.

So I propose the following to allow admins to have a choice:

1) Rename hot-backup.py to hot-backup-db.py. No other changes.
2) Create a new hot-backup-repos.py script that creates a single
   file using svnadmin dump --incremental for each revision in the
   repository. The filename will have a format
      svn-dump-v%d-rev%d
   Here the first %d is the SVN-fs-dump-format-version format
   number and the second %d is the revision number.

   The backup program will go through each revision in the
   repository and dump that revision if the file does not
   exist. When there's an upgrade to the dump file format,
   the program will automatically create all the revision
   dumps automatically because the files will not exist.

   Obviously, revision 0 will not use the --incremental option.

Best,
Blair

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