Add support to specify retention period while taking backups
General
Escalation
General
Escalation
Description
While laying out a backup policy, the requirement sometimes comes out to be like this
Daily backups need to be stored for a week
Weekly backups need to be stored for a month
Monthly backups need to be stored for 12 months
While the delete backup command has a useful --older-than flag, it's not very helpful when it comes to specifying the above strategy.
Managed services like Atlas already have something like this, where we can specify both the frequency and the retention period of the backups. (Refer to the screenshot)
Environment
None
Attachments
1
Smart Checklist
Activity
Show:
Divyansh Rai January 26, 2022 at 9:57 AM
Hi Sergey,
That makes sense. I wasn't aware that it was already there on Kubernetes Operator. You're correct, having it in PBM is unnecessary for sure.
Thanks for the reply. Can we mark this as not applicable?
Sergey Pronin January 24, 2022 at 1:25 PM
Hello . Thank you for this request.
We see our software as a building blocks. Percona Backup for MongoDB (PBM) is one of these blocks that can be used to do something great.
Retention policy is something that we already have in Kubernetes Operator and plan to have it in Percona Monitoring and Management later on.
Implementing this logic in PBM would overcomplicate it.
While laying out a backup policy, the requirement sometimes comes out to be like this
Daily backups need to be stored for a week
Weekly backups need to be stored for a month
Monthly backups need to be stored for 12 months
While the delete backup command has a useful --older-than flag, it's not very helpful when it comes to specifying the above strategy.
Managed services like Atlas already have something like this, where we can specify both the frequency and the retention period of the backups. (Refer to the screenshot)