Retention Policy for Backups

For image-level backups, Veeam Backup for GCP retains restore points for the number of days defined in backup scheduling settings

To track and remove outdated restore points from a backup chain, Veeam Backup for GCP performs the following actions once a day.

  1. Veeam Backup for GCP checks the configuration database to detect GCP storage buckets that contain outdated restore points.
  2. If an outdated restore point exists in a storage bucket, Veeam Backup for GCP transforms the backup chain in the following way:
  1. Veeam Backup for GCP rebuilds the full backup file to include there data of the incremental backup file that follows the full backup file. To do that, Veeam Backup for GCP injects into the full backup file data blocks from the earliest incremental backup file in the chain. This way, the full backup ‘moves’ forward in the backup chain.

 

Retention Policy for Backups 

  1. Veeam Backup for GCP removes the earliest incremental backup file from the chain as redundant — this data has already been injected into the full backup file.

 

Retention Policy for Backups 

  1. Veeam Backup for GCP repeats step 2 for all other outdated restore points found in the backup chain until all the restore points are removed. As data from multiple restore points is injected into the rebuilt full backup file, Veeam Backup for GCP ensures that the backup chain is not broken and that you will be able to recover your data when needed.

 

Retention Policy for Backups 

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.