Limitations and Considerations for GFS Cycles

In this article

    Before configuring the GFS retention policy for a backup copy job, mind the following limitations and considerations:

    General Settings

    Mind the following for general settings of a backup copy job:

    Periodic Copy Mode

    If you want to use the periodic copy mode, mind the following:

    • If the backup copy interval is not enough to get the active full backup, the interval will be prolonged until the active full process is finished.
    • Veeam Backup & Replication creates a GFS full backup even if the GFS full backup creation is scheduled when the backup copy interval is not finished. On the day when the GFS full backup must be created, Veeam Backup & Replication shows a warning that the current backup copy interval will be completed, completes the interval, and starts a new one. The way how Veeam Backup & Replication behaves further depends on the selected backup copy GFS method:
    • In case of the synthetic full method, Veeam Backup & Replication first copies data for an incremental backup from the source backup repository and then, on the target backup repository, synthesizes the GFS full backup using this data and data of the already stored backup files.
    • In case of the active full method, Veeam Backup & Replication copies data for the GFS full backup from the source backup repository and creates the GFS full backup on the target backup repository.

    Changes in GFS Retention After Upgrading from Veeam Backup & Replication 10 to version 11

    In Veeam Backup & Replication version 11, the backup copy GFS retention settings are different from the settings in version 10. If you upgrade to Veeam Backup & Replication 11, all GFS retention settings of existing backup copy jobs are automatically switched to the new format with minimal changes:

    If the monthly GFS schedule was set to a period between the 3rd Monday and last Sunday, in version 11 the monthly GFS settings is changed to Last week.

    If in version 10 the yearly GFS schedule was set to the first-fourth Monday-Sunday of the year, in version 11 the schedule is changed to the first day of January.

    If the yearly GFS schedule was set to the last Monday-Sunday of the year, in version 11 the schedule is set to the first day of December.

    If in version 10 the quarterly GFS policy was enabled, in version 11 three additional months are added to the monthly GFS policy to compensate the quarterly full backups.

    If in version 10, the GFS policy was set to X monthly backups and Y quarterly backups. Then, in version 11, the retention policy is switched to store monthly backups for (X + 3Y) months.


    [For synthetic method] If you upgrade to Veeam Backup & Replication 11, the next GFS full backup will be created from the latest backup chain according to a new schedule. The old GFS candidate may be deleted by short-term retention. To avoid losing the GFS restore point, make sure that the chain does not contain incremental points for the days when the future GFS restore points are scheduled.

    We recommend to schedule the upgrade to version 11 right after the latest GFS restore point is created. You can also decrease the short-term retention temporarily to force the merge and creation of the GFS restore point.

    I want to report a typo

    There is a misspelling right here:


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