Ability to create custom backup retention schedule presets
-
Please allow to enter an own retention schedule and not only their few presets. Or if easier, at least add a few more that make sense, which are not covered.
Such as keeping...
- Yearly's for X years, monthly per year, daily per month
- Half-yearly's for X years, bi-weekly per Y months, daily per Z days.
I found this to be common practice in various companies I was working in.
-
Please allow to enter an own retention schedule and not only their few presets. Or if easier, at least add a few more that make sense, which are not covered.
Such as keeping...
- Yearly's for X years, monthly per year, daily per month
- Half-yearly's for X years, bi-weekly per Y months, daily per Z days.
I found this to be common practice in various companies I was working in.
-
How valuable would this be in practice? I.e. how often and in what cases would you need to restore very old spaced out backups like this?
Not that the features are mutually exclusive, but personally I think I would prefer the ability to pin specific app or full backups on demand instead of having a more complex retention schedule like this. That way I could save the backup right before an upgrade, or the one before and after making big changes in the app. Such backups would be much more useful than hoping that the backup you needed was retained at the right point in the schedule without data loss.
-
How valuable would this be in practice? I.e. how often and in what cases would you need to restore very old spaced out backups like this?
Not that the features are mutually exclusive, but personally I think I would prefer the ability to pin specific app or full backups on demand instead of having a more complex retention schedule like this. That way I could save the backup right before an upgrade, or the one before and after making big changes in the app. Such backups would be much more useful than hoping that the backup you needed was retained at the right point in the schedule without data loss.
@infogulch If you think about a small number of service, you can adopt a case by case basis approach like you mention.
When you change the scale or host third parties, it's much easier to not have to rely on your judgement and the human, and systemize the process of backing up, with multiple close to the present, and space out more and more as the time passes.
-
How valuable would this be in practice? I.e. how often and in what cases would you need to restore very old spaced out backups like this?
Not that the features are mutually exclusive, but personally I think I would prefer the ability to pin specific app or full backups on demand instead of having a more complex retention schedule like this. That way I could save the backup right before an upgrade, or the one before and after making big changes in the app. Such backups would be much more useful than hoping that the backup you needed was retained at the right point in the schedule without data loss.
@infogulch a hybrid of both would be best, but let's start with this one.
If CL is going to be more adopted in the enterprise, it will need better audit & retention capabilities before things go to archive.
