First off, thanks much for a wonderful module. This is always on my short list of "must haves". Great stuff. Please excuse if this has been requested before. I did look for it and did not notice any similar requests.

I'm envisioning a tiered auto delete schedule. Assume a backup is made every 24 hours. These would be kept for 14 days. Files over 14 days old would be selectively deleted; perhaps only those performed on Fridays would be retained. When the weekly backups reach three months old, only one per month is kept.

It's a little hit-or-miss, but what used to require 364 files gets slashed to only 35 (14 daily + 12 weekly + 9 monthly). With high traffic sites who perform more regular backups, this tiered approach could save a tremendous amount of storage space and administration time.

I'm not seeing this so much as for restoring the site, but it could be extremely useful in a staging environment for locating returning users or finding fragments of deleted content.

Thanks for considering!

-NP

Comments

ronan’s picture

ronan commented
Status: Active » Closed (won't fix)

I see the need here but I'm not sure I'd want to encode that much logic in the module since your particular set of rules might not work for the next guy and the user interface to configure such a plan could end up being a little complex.

You could create the plan you describe using 3 different backup schedules. The problem there is that once a month you'd have the potential of backup and migrate attempting to run all three schedules during the same cron run which could time out. I'm pretty sure in that case the schedule which timed out would attempt to run on the next cron run, so it might be a moot issue.

Having the cron-like scheduling described in #313134: Allow setting scheduled time similar to cron job would fix this issue though, letting you run your daily backups on every day except friday, and your weekly only on friday, etc.

I'm marking this as won't fix since if I can get the above ticket done I believe you'd have enough control to implement the scheme you describe and I would not have to hard code any of your logic into the module.

nonprofit’s picture

nonprofit commented

Thanks ronan!

ronan’s picture

ronan commented
Status: Closed (won't fix) » Active

I am reopening this because I'm liking the idea more and more.

nonprofit’s picture

nonprofit commented

Cool

ronan’s picture

ronan commented
Version: 6.x-2.x-dev » 7.x-3.x-dev
Status: Active » Fixed

Something similar to this is now built into b&m 3

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.