foggy wrote:Hi Tom and welcome to the community forums. To achieve what you want you can just enable GFS retention in the backup copy job and configure it to keep 12 monthly backups, each of them will be a separate full backup file. If you want it to land on another repository (not the same that the backup copy job points to), you can use another copy job for that, however, do you really need it to be another repository?
Thanks. The logic behind another repository was due to the way I plan to implement things.
Initially, I will be putting a single server with local storage both on site and off site. This is to provide 1 month of daily backups via the forward incremental plan, retaining each sundays full backup until the 1 month is up. I am going to use a copy job to replicate this offsite as well.
Stage 2 is to implement the monthly backup copy plan with 12 month retention. If I am able to expand the original repositories with extra disks then I shall do that. Otherwise I figured I might need a separate repository for the 12 month plan.
The 30 days forward incremental plan.... Am I right in thinking this will take its initial backup, then 6 incrementals, and on the 7th day, (depending on synthetic or active) will merge the previous incrementals into a new full backup. I need to retain every one of these weekly full backups until the 30 days is up, is this possible?