Configuring Global Retention Settings

In this article

    Veeam Backup for Microsoft Azure allows you to configure global retention settings to specify for how long the following data must be retained in the configuration database:

    Configuring Retention Settings for Obsolete Snapshots

    If an Azure VM is no longer processed by a backup policy (for example, it was removed from the backup policy or the backup policy no longer exists), its snapshots become obsolete. Retention policy settings specified in backup policy settings do not apply to obsolete snapshots — these snapshots are removed from Veeam Backup for Microsoft Azure according to their own retention settings.

    To configure retention settings for obsolete snapshots, do the following:

    1. Switch to the Configuration page.
    1. Navigate to Settings > Retention Settings.
    1. In the Obsolete snapshots retention section, select one of the following options:

    This option is selected by default.

    If you select this option, Veeam Backup for Microsoft Azure will first wait for the specified period of time after an Azure VM stops being processed by a backup policy, and then will remove its obsolete snapshots from the configuration database as soon as the period is over.

    1. Click Save.

    Configuring Retention Settings for Session Records

    Veeam Backup for Microsoft Azure stores records for all sessions of performed data protection and disaster recovery operations in the configuration database. These session records are removed from Veeam Backup for Microsoft Azure after 365 days by default. However, you can configure retention settings for the records.

    1. In the Session retention section of the Retention Settings page, select one of the following options:

    If you select this option, Veeam Backup for Microsoft Azure will remove all session records that are older than the specified time limit.

    1. Click Save.

     

    Configuring Retention Settings

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.