Feature #2168

Backup: Retention policy based on disk size

Added by Alessio Fattorini almost 8 years ago. Updated about 6 years ago.

Status:CLOSEDStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:nethserver-backup-data
Target version:~FUTURE
Resolution:REJECTED NEEDINFO:No

Description

There is a retention policy yet based on time.
CleanupOlderThan : time to retain backups, accept duplicity syntax (eg. 7D, 1M). Default is: never (keep all backups)

We can add a retention policy based on destination disk size, calculating free space and removing older backup set before create new backup.
Does Duplicity support it?

History

#1 Updated by Giacomo Sanchietti almost 8 years ago

We can add a retention policy based on destination disk size, calculating free space and removing older backup set before create new backup.
Does Duplicity support it?

The idea is cool, but duplicity doesn't support it. The implementation could be done in post-backup-* event, but I see some problems:
  • you'll never know if freed space will be enough for the new backup
  • let's assume it's time to delete old backups, which one do you want to delete? Backups older than CleanupOlderThan?
  • there is no way (or it's really really hard) to calculate free space for targets like Amazon S3, Cloudfiles, webdav, etc. Maybe this kind of policy make sense only for certain targets

#2 Updated by Giacomo Sanchietti about 6 years ago

  • Status changed from NEW to CLOSED
  • % Done changed from 0 to 100
  • Resolution set to REJECTED

It's very hard to implement, no reason to keep this open.

Also available in: Atom PDF