Restore points in the backup chain are not kept forever. They are removed according to the retention policy. The retention policy helps maintain the life cycle of restore points and make sure that backup files do not consume the whole disk space.
Veeam Endpoint Backup retains restore points for the last N days; the number of days is defined by the user. During every backup job session, Veeam Endpoint Backup checks if there is any obsolete restore point in the backup chain. If some restore point is obsolete, it is removed from the chain.
For retention policy settings, Veeam Endpoint Backup takes into account not calendar days but days on which backup files were successfully created.
For example, you have configured the backup job in the following way:
- The backup job runs daily.
- The retention policy is set to 5 days.
The backup job has successfully run 3 times and created 3 restore points in the backup chain. After that, you have turned off your computer for 10 days. When you turn on your computer, Veeam Endpoint Backup runs a backup job by schedule and creates a new restore point. The earliest restore point, however, is not removed from the backup chain. At the end of a new backup job session, the backup chain will have only 4 restore points created during 4 days when the backup job was successfully run.
Removing Backups by Retention
When removing obsolete restore points, Veeam Endpoint Backup does not simply delete backup files from disk. It transforms the backup chain so that the backup chain always contains a full backup file on which subsequent incremental backup files are dependent. To maintain the consistency of the backup chain, Veeam Endpoint Backup uses the following rotation scheme:
- During every backup job session Veeam Endpoint Backup adds a backup file to the backup chain and checks if there is an obsolete restore point.
- If an obsolete restore point exists, Veeam Endpoint Backup transforms the backup chain. As part of this process, it performs the following operations:
- Veeam Endpoint Backup re-builds the full backup file to include in it data of the incremental backup file that follows the full backup file. To do this, Veeam Endpoint Backup 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.
- The earliest incremental backup file is removed from the chain as redundant: its data has already been injected into the full backup file, and the full backup file includes data of this incremental backup file.
If the backup chain contains several obsolete restore points, the rebuild procedure is similar. Data from several restore points is injected to the re-built full backup file. This way, Veeam Endpoint Backup makes sure that the backup chain is not broken, and you will be able to recover your data to any restore point.