Shestakov wrote:That confused me a bit. To meet your initial goal you need to set Restore points to keep = 31, Monthly backup = 12, Yearly backup = 7.
foggy wrote:Both approaches are viable. Just keep in mind that setting job retention to just a single restore point (regular job in the first approach) is not recommended, as you might find yourself without any valid restore point at all.
Sorry about that, I'll try to explain.
Based on the advice from foggy (thanks BTW) rather than have the 31 Restore Points (as I said I might do in my first post on the topic) on the Backup Copy job, I will have the 31 Restore points on the actual Backup Job, which will reside on a Repository for the month worth of restore points (the 31).
I will then configure the Backup Copy job to only hold 2 Restore points, but using GFS i'll set it to have 12 Monthly restore points and 7 Yearly restore points; set to generate on the Last day of the month and Last day of December. So, at the end of the first 12 months (my calculations and for the sake of theory, we started the schedule in Janurary), the Repository holding the Backup Copy job will have 1 Full backup and a VIB (for the 2 restore points) and an additional 12 Full backup files. The last full backup file being tagged as an end of month and the first yearly.