Feature for repozo: when making full backup, clean up all old backups.

[Chris McDonough]

The attached patch to the current repozo.py in Zope 2.7 branch provides an additional command line option:

    -k / --kill-old-on-full
        If a full backup is created, remove any prior
        full or incremental backup files (and
        associated metadata files) from the
        repository directory.

This change is to make repozo "clean up after itself" as it creates backups through time (without the feature, a repository directory grows without bound).

[Andreas Jung (ajung)]

Please put it into the CVS. You have CVS access :-)

[Chris McDonough (chrism-plope)]

I don't change things in CVS/SVN that relate to ZODB, mostly because I don't know where I would need to replicate the checkin across all the places it lives.

[Jens Vagelpohl (dataflake-deactivatedaccount-deactivatedaccount)]

Suggestion: Make the switch accept a number describing the number of "generations" to keep. No one just keeps a single generation of backups around...

[Chris McDonough (chrism-plope)]

Fine by me, although it works pretty well for me now (I have a file backup routine that is generational, so this doesn't need to be).

[Eddie Butcher (ebutcher)]

What would be most useful is the ability to specify the number of backup files *kept*.

[Chris McDonough (chrism-plope)]

Yup, heard that the first time around <wink>. Again, most regular folks have backup systems that are already generational. Is anyone willing to try the patch to see if it meets their needs before engineering this thing into oblivion? ;-)

[Tres Seaver (tseaver)]

I have checked in this patch, with tests, on the following branch:

 http://svn.zope.org/ZODB/branches/tseaver-lp143158-feature/?rev=106808&view=rev

Please review and merge.

[Tres Seaver (tseaver)]

Merged to trunk for the 3.10.0a2 release:

  http://svn.zope.org/ZODB/trunk/?rev=110913&view=rev

[Tres Seaver (tseaver)]

Released in ZODB 3.10.0a2:

  http://pypi.python.org/pypi/ZODB3/3.10.0a2#a2-2010-05-04