VM Backup Retention

For image-level backups, Veeam Backup for Google Cloud retains restore points for the number of days defined in backup scheduling settings as described in section Creating VM Policies.

To track and remove outdated restore points from a regular backup chain, Veeam Backup for Google Cloud performs the following actions once a day:

1. Veeam Backup for Google Cloud checks the configuration database to detect standard and nearline repositories that contain outdated restore points.
2. If an outdated restore point exists in a backup repository, Veeam Backup for Google Cloud deploys a worker instance in a Google Cloud region in which the repository with backed-up data resides.
3. Veeam Backup for Google Cloud transforms the regular backup chain in the following way:

1. Rebuilds the full backup to include there data of the incremental backup that follows the full backup. To do that, Veeam Backup for Google Cloud injects into the full backup data blocks from the earliest incremental backup in the chain. This way, the full backup ‘moves’ forward in the regular backup chain.

2. Removes the earliest incremental backup from the chain as redundant — this data has already been injected into the full backup.

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

5. Veeam Backup for Google Cloud removes the worker instance when the retention session completes.

Related Topics

Retention Policy for Archived Backups