Skip to main content
  • EN

We observed our monthly back ups were deleted earlier than the 3 month retention set in the jobs .

 

Short term retention is 35 restore points

GFS is 3 months 

Repo is SOBR extents - Exagrid 

  • GFS Policy: Enabled, monthly backups kept for 3 months.
  • Active full backup: Scheduled last monday of every month.
  • Transform to synthetic full: Scheduled first sunday of every month.
  • VSS settings: Application aware processing is enabled.

 

 

We need to understand why the retention policy is not working as expected. Could you please provide a checklist of items to investigate, and explain whether the current settings would result in this behavior?

Thanks all for the inputs. One last question ,is there a way we could configure it to retain the last day of the month full back up?

Not the specific day unless it falls in the weekly used for the monthly backup.

Thanks all for the inputs. One last question ,is there a way we could configure it to retain the last day of the month full back up?

Not the specific day unless it falls in the weekly used for the monthly backup.

Thanks. or else we need to disable synthetic backup , in order for AF to be GFS ?

Thanks all for the inputs. One last question ,is there a way we could configure it to retain the last day of the month full back up?

Not the specific day unless it falls in the weekly used for the monthly backup.

Thanks. or else we need to disable synthetic backup , in order for AF to be GFS ?

It will depend on the settings and how you have it set up.  Typically I use either Synthetic or AF but not both.  I use Synthetic if I am using ReFS/XFS repos with fast clone, otherwise I use AF.  If only AF then depending on when that runs and falls in to the GFS schedule will determine it.

Hi ​@Nikks - Using Synth vs AF depends on a couple factors as I shared why earlier, and Chris shares above. 

What do you mean is there a way to retain the last Full of the month? You can configure to create your Fulls on which day each month. If you mean for GFS, I don’t think so. You may have to reach out to Support for that question.

Best.

I don’t think that is the reason ​@Nikks . Deleted Items only refers to VM objects in a Job which have been removed from a Job and are no longer processed. So, if you remove “VM-A” from your Job, it is removed after 30 days only after it meets certain criteria, one of which if it is no longer part of an active backup chain.

See: https://helpcenter.veeam.com/docs/backup/vsphere/retention_deleted_vms.html?ver=120

Thanks for the clarification. Disk properties shows M 

 

If you are set to GFS with 3 monthly, this is working as expected with the 3 monthly jobs being retained.  I believe you specified active full end of month in your post. 

 

If one of the other VM’s were added later, it’s possible they may have less restore points, or if a VM was removed from the job, the 30 day deletion will come into effect. 

 

 

 

Comment


Terms & Conditions