This is an archive version of the document. To get the most up-to-date information, see the current version.Weekly Backup Cycle
In the GFS scheme, the weekly backup is created during the weekly backup cycle.
Weekly backup cycles always produce full backup files that contain data of the whole VM image as of specific date. When you define retention policy settings for the weekly backup cycle, you specify how many weekly backups you want to retain and define the week day on which the weekly full backup must be created.
Veeam Backup & Replication creates weekly full backups for synthetic and active full backup methods in different ways:
Veeam Backup & Replication creates a weekly full backup in the following way:
- With every new synchronization interval, Veeam Backup & Replication transforms the backup chain and moves the full backup forward. This procedure repeats until the full backup file reaches the day when the weekly backup is scheduled.
- During the synchronization interval on this day, Veeam Backup & Replication transforms the backup chain and creates a weekly full backup at the same time. This process is performed in the following way:
- Veeam Backup & Replication adds a new restore point to the backup chain.
- As the allowed number of restore points is exceeded, Veeam Backup & Replication transforms the backup chain. The transformation process slightly differs from a regular one. Veeam Backup & Replication does not inject data from the incremental backup to the full backup. Instead, it copies data from full and incremental backups and stores them to a new full backup file, next to the primary backup file.
- The primary full backup file remains on the target backup repository. Veeam Backup & Replication sets it aside and marks it as a weekly full backup. The weekly backup is no longer used in the backup chain.
- The newly created full backup file remains in the backup chain and is used as a starting point for incremental backups created by the regular backup cycle.
