Create Active Full Backup Periodically - How is it groomed?

[TGacs]

v9.5 U2

Under <BackupJob> > Advanced > Backup > Active full backup > Create Active Full Backup Periodically checkbox

Backup mode is currently set to Forward Incremental with weekly Create Synthetic Full & Transform Previous to Rollbacks.

Suppose I now enable monthly active full backups.

1) What controls the periodic grooming of these active full backups off of the repository? (i.e., how do they get auto-deleted over time? / how do I control how many months worth are retained?)

2) Would these Active Full backups interact with the current chain of vib/vbk/vrb files in the job, or would the Active Fulls be "standalone" backups?

[Shestakov]

Active fulls restore points are deleted with the same logic as incrementals, i.e. oldest restore points are to be deleted. As for the chain, when new full restore point is created, the increments will start new chain from this vbk.
Thanks!

[foggy]

Basically, active and synthetic fulls are completely similar in terms of retention, only data source is different.

[TGacs]

So, grooming is controlled by the job value Restore Points to keep on disk?

[Shestakov]

Correct

[wormdoc]

Hi there, Hate to bring up an old topic but makes more sense than opening a new one.

So if you wanted to retain your monthly backups would you create a separate Monthly Job and say you wanted to keep each month for a year just setup 12 restore points?

[EugeneK]

In case of monthly backup files retention, it would be beneficial to consider the use of GFS policy with Backup Copy jobs functionality. For more details on how GFS policy is applied to Monthly backups please use this link

[wormdoc]

Great, thank you for that.
I Have setup a backup copy job now and ticked: Keep the following restore points as full backups for archival purposes

and put 12 in the monthly backup .

Does my standard backup job need to have an active full for this to work? or will it be able to use the synthetic full?

[veremin]

No, it does not, as backup copy will synthesize required restore points in "target" repository from VM data in source backup repositories regardless whether the last point available there is full or incremental one. Thanks!