For reversed incremental backup chains, Veeam Backup Enterprise Manager keeps more indexing data in the Veeam Backup Catalog than it may seem to be required according to the retention policy. This happens due to backward nature of reversed incremental backups.
When Veeam Backup Enterprise Manager deletes indexing data by retention, it removes the whole set of files: VM indexing data and session indexing data. Before removing indexing data for a specific VM restore point, Veeam Backup Enterprise Manager makes sure that this restore point is not referenced by any of backup job sessions:
- If no relations are detected, indexing data for this VM restore point is removed from Veeam Backup Catalog.
- If the VM restore point is referenced by any backup job session, indexing data for this VM restore point remains in Veeam Backup Catalog
However, in reversed incremental chains, session indexing data references the VM restore point that was created in the backup job sessions, and restore points preceding it. To learn more, see Session Indexing Data.
For this reason, Veeam Backup Enterprise Manager retains more indexing data for reversed incremental chains. The retention period is calculated by the following formula:
Retention period = MAX (Catalog Retention, X)+X,
- Catalog Retention is the retention period specified in Veeam Backup Enterprise Manager
- X is the amount of time for which restore points are kept by a backup jobs
For example, the retention policy settings are specified in the following manner:
- The retention policy for the backup job is set to 3 points. The backup job is run daily.
- The retention period in Veeam Backup Enterprise Manager is set to 1 month, or 30 days.
In this case, Veeam Backup Enterprise Manager will retain in Veeam Backup Catalog indexing data for 30 days plus indexing data for 3 VM restore points in the backup chain.
The longer is the backup chain, the more indexing data is stored in Veeam Backup Catalog.