Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pruning of old backups #26

mzpqnxow opened this Issue Feb 14, 2019 · 0 comments


None yet
1 participant
Copy link

mzpqnxow commented Feb 14, 2019

There is a similar project here which uses a very convenient pruning logic to ensure short-term backups, long-term backups, and pruning of "old" backups using this logic:

Backup sets are automatically deleted following a simple expiration strategy > > defined with the --strategy flag. This strategy is a series of time intervals > with each item being defined as x:y, which means "after x days, keep one backup > every y days". The default strategy is 1:1 30:7 365:30, which means:

  • After 1 day, keep one backup every 1 day (1:1).
  • After 30 days, keep one backup every 7 days (30:7).
  • After 365 days, keep one backup every 30 days (365:30).

Before the first interval (i.e. by default within the first 24h) it is implied > that all backup sets are kept. Additionally, if the backup destination > directory is full, the oldest backups are deleted until enough space is > available.*

This would be a great feature to have, but may be beyond the scope of the intent of this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.