Skip to main content
  • EN

Hello,

We have a Backup Copy on S3 containing multiple backup jobs, and we have noticed that VMs removed from the jobs are not being deleted from the S3 repository, even after exceeding the defined retention period. Full and incremental backup images are still being retained.

I would like to understand how retention works in this scenario. Does the fact that the backup chain is incomplete prevent the deletion of old restore points?

What are the best practices to ensure the automatic expiration of obsolete backups?

Thank you in advance for your help.

Best regards,

Hi ​@asaadidi -

Have you looked at the User Guide on Backup Copy Job Retention and how it works?

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

And Deleted Items Retention:

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

As stated in the 2nd link for Deleted Items, and as you thought...if an item/restore point is part of an active chain needed for recovery, then it won’t be removed until a subsequent chain is created. Also, take note of the “Important” section. Deleted Items Retention also only applies to “regular” (i.e. Short-Term) Copies, not GFS.

Hope this helps.

Best.

Veeam's backup retention works by deleting older restore points based on the defined policy, provided the backup chain remains intact. Once a new backup is created, outdated backups are removed according to the retention settings. 

If a VM is removed from a Backup Copy job, the backup chain may break, preventing automatic deletion of its restore points. In such cases, backups may persist in the repository beyond the retention period. To manage this, enable "Remove deleted items data after X days" or manually delete orphaned backups. 

This design ensures that backups remain available for VMs that were unexpectedly decommissioned or lost, allowing recovery when needed. However, if a VM is intentionally removed and its backups are no longer required, you must manually delete the data to free up storage and maintain a clean repository.

Comment


Terms & Conditions