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 standard backup chain, Veeam Backup for GCP performs the following actions once a day:
- Veeam Backup for GCP checks the configuration database to detect standard backup repositories that contain outdated restore points.
- If an outdated restore point exists in a repository, Veeam Backup for GCP transforms the standard backup chain in the following way:
- 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 standard backup chain.
- 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.
- Veeam Backup for GCP repeats step 2 for all other outdated restore points found in the standard 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 standard backup chain is not broken and that you will be able to recover your data when needed.