Retention Policy for Backups

In this article

    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 sections Creating VM Policies and Creating SQL Policies.

    To track and remove outdated restore points from a standard 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 backup 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 standard backup chain in the following way:
    1. 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 Google Cloud 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.

     

    Retention Policy for Backups 

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

     

    Retention Policy for Backups 

    1. Veeam Backup for Google Cloud 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 Google Cloud ensures that the standard backup chain is not broken and that you will be able to recover your data when needed.

     

    Retention Policy for Backups 

    1. Removes the worker instance when the retention session completes.

    Notes

    Each worker instance can process only one retention task at a time, and Veeam Backup for Google Cloud can simultaneously deploy maximum 10 worker instances to process retention tasks. If the number of retention tasks that must be processed by worker instances is more than the specified limit, the tasks exceeding this limit are queued.

    Related Topics

    Retention Policy for Archived Backups