-
Notifications
You must be signed in to change notification settings - Fork 5
Description
In the inspiration you linked they touch on having a unique script call for daily snapshots and lower frequency snapshots.
I would like to implement a varying frequency backup call. For example, in the previous day keep a backup every hour, in the previous week keep a backup every day, in the previous month keep a backup every week, etc.
I can certainly fork the repository and implement this logic. But it would make sense to push the changes upstream.
Given this, how would you approach the logic to cause zero changes to old .conf files?
I can see some changes would be needed in the functions deleteOld<XXX>Backups to include an additional argument to filterFilesToDelete. Additionally I would need to rebuild filterFilesToDelete to account for this logic.
Let me know if you have any ideas, I'll start building on the logic in the week.
Thanks.