Sorry for taking so long to getting back to you.
Example, if I started doing backups in September, today I would have those backups:
The image is just an example, in real life I did the monthly backup 2sd Saturday, and the yearly 4th Saturday of May. I still have overlap, but a little less, without adding too much complexity to the solution.
Thank you all!
It seems a bit complicated, but doable. I ended up doing 3 tasks, daily, monthly and yearly. I just ignored the overlap, would be nice and more elegant to take it into consideration, but I had more pressing issues to deal with, I had to prioritize.On the monthly and daily you could run a external script of some sort to test if one of the other backups has already been run or when the month or year backups run create files that are tested and deleted by a script on the other backups so they know to skip today's backup. But I see no way to do it totally within Cobian.
The data I want to keep it's the retention specified by the software provider, the one shown in the image, 15 daily backups, 3 monthly backups and 3 yearly backups.How many cycles you set the retention to is dependent on how much data you want to keep in retention.
Example, if I started doing backups in September, today I would have those backups:
In the image you can see the way I do every 1st of September I do 3 backups of the same data, once because of the daily backup, another because of the monthly and a third for the yearly. Every 1st, there is a overlap, duplication, of the daily and monthly backup.Sorry but I don't understand your question. What do you mean by backup overlap ?
The image is just an example, in real life I did the monthly backup 2sd Saturday, and the yearly 4th Saturday of May. I still have overlap, but a little less, without adding too much complexity to the solution.
Thank you all!
Statistics: Posted by noki — 04 Sep 2024, 01:00