That's what we have GFS retention for. If you want to keep incrementals as well then you should either stick with File Copy Job or use some custom post-job scripts to copy the chain offsite and update it every time the job is finished.The 2nd copy will likely be given a longer retention.
However there is a workaround provided by Tom:Back to the main question, can jobs be layered/stacked in the way described in the opening post?
Tom Sightler wrote:Backup Job is configured to backup to Repo1
Backup Copy Job 1 is configured to use Backup Job as selected object (I don't think this matters could use Infrastructure, Job, or Backup to select the objects), and then the "Source" button is used select only "Repo1" as the source repo. The job copies restore point from "Repo1" to "Repo2".
Backup Copy Job 2 is configured to use Backup Job as selected object just like BCJ1 (once again, don't think this matters), and then "Source" button is used to select only "Repo2" as the source repo. This job copies the points from "Repo2" to "Repo3".
This configured seems to work in light testing, so I think the question is whether there are any issues that might be a problem with this configuration.
Users browsing this forum: Bing [Bot], Google [Bot] and 1 guest