EC2 Backup Retention
For image-level backups, Veeam Backup for AWS 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 AWS performs the following actions once a day:
- Veeam Backup for AWS checks the configuration database to detect backup repositories that contain outdated restore points.
- If an outdated restore point exists in a backup repository, Veeam Backup for AWS performs the following operations:
- If the total size of backup files that must be deleted is more than 1 TB, launches a worker instance in an AWS Region where the backup repository is located to process a retention task. Otherwise, Veeam Backup for AWS processes the task on the backup appliance.
By default, Veeam Backup for AWS uses the default network settings of AWS Regions to launch worker instances. However, you can add specific worker configurations. For more information on worker instances, see Managing Worker Instances.
- Transforms the backup chain in the following way:
- Veeam Backup for AWS rebuilds the full backup file to include in it data of the incremental backup file that follows the full backup file. To do that, Veeam Backup for AWS injects into the full backup file data blocks from the earliest incremental backup file in the chain. This way, a full backup ‘moves’ forward in the backup chain.
- Veeam Backup for AWS 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 AWS 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 AWS ensures that the backup chain is not broken and that you will be able to recover your data when needed.
- If the worker instance was launched, Veeam Backup for AWS removes this worker instance from Amazon EC2 when the retention session completes.
Mind the following: