So as I understand it a backup without a schedule will never process old restore points in line with the retention policy.
The scenario we have is a customers backups have grown considerably over time so we have now split the backups into smaller jobs to spread out the workload.
We need to retain the existing backup job for compliance while the new ones start taking backups but is there a way to get the old one to process the old backups and remove them when there is no schedule?
-
- Service Provider
- Posts: 22
- Liked: never
- Joined: May 26, 2020 8:26 am
- Full Name: Matthew Humphreys
- Contact:
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Retention policy on backups without a schedule
Hi Matthew
With V11, GFS restore point retention will be processed in the background, even without an active backup job.
Veeam Guide - Background GFS Retention
That should help you to automatically get rid of the older gfs restore points of the removed vms from the backup job.
With V11, GFS restore point retention will be processed in the background, even without an active backup job.
Veeam Guide - Background GFS Retention
That should help you to automatically get rid of the older gfs restore points of the removed vms from the backup job.
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 22
- Liked: never
- Joined: May 26, 2020 8:26 am
- Full Name: Matthew Humphreys
- Contact:
Re: Retention policy on backups without a schedule
Hi Mildur,
Brilliant thanks, even though the backup doesnt run its good to know that it will be processed for retention anyway, we have it set to 14 days as it us so it should age out as it has previously because of our synthetic full schedule we usually end up with 21 restore points in one cycle.
Brilliant thanks, even though the backup doesnt run its good to know that it will be processed for retention anyway, we have it set to 14 days as it us so it should age out as it has previously because of our synthetic full schedule we usually end up with 21 restore points in one cycle.
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Retention policy on backups without a schedule
Please keep in mind that background GFS retention works for VMs that are not covered by a job anymore - if your requirement is to keep the old job with all VMs in it, that wouldn't help.
-
- Chief Product Officer
- Posts: 31812
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Retention policy on backups without a schedule
Actually, there's no such limitation as "works for VMs that are not covered by a job anymore" only.
He can keep the old job disabled, in fact this is exactly the scenario from What's New for V11 (p. 7)
He can keep the old job disabled, in fact this is exactly the scenario from What's New for V11 (p. 7)
Who is online
Users browsing this forum: Semrush [Bot] and 114 guests