Semi-OT, since I don't use c.r.backup for my blobs (I'm using RelStorage now), but:
I have had good luck with a shell script template I created for use with collective.recipe.template to create script in bin I cron for a set of N-day rsync snapshots of blobs: http://bazaar.launchpad.net/~upiq-dev/upiq/plone41deployment/view/head:/app/src/build/blobrsync.sh.in [paths] var = ${buildout:directory}/var [blobrsync] recipe = collective.recipe.template input = ${buildout:directory}/src/build/blobrsync.sh.in output = ${buildout:bin-directory}/blobrsync.sh blobdir = ${paths:var}/blobstorage backupdir = ${paths:var}/backups Sean On Fri, Sep 9, 2011 at 4:48 AM, Gil Forcada <[email protected]> wrote: > Hi, > > I'm enjoying c.r.backup a lot, actually it saved my day thanks to the new > version with blob backups! > > One thing I noticed though is that keeping all defaults[1] the only folder > that gets cleaned is var/snapshotbackups, the other backup/snapshot folders > keep growing and growing: > - var/backups (incremental backups) > - var/blobstoragebackups (incremental blob backups) > - var/blobstoragesnapshots (full blob backups) > > Was it meant to be like this or is just because a .0 release is always > waiting for a .1 to enhance the release? :) > > Cheers, > > [1] > parts = > backup > > [backup] > recipe = collective.recipe.backup > > > -- > > *Gil Forcada** > *C/Llacuna, 166 2n.2a (Edifici Llacuna) > telf: 93.188.88.12 - 619.65.34.92 > fax: 93.320.93.97 > (08018) BARCELONA > [email protected] > www.usecm.com > > > _______________________________________________ > Product-Developers mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/plone-product-developers > >
_______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
