Skip to main content

Archive Backup Retention (GFS)

Last update:

GFS (Grandfather-Father-Son) archive retention is an algorithm for long-term storage of selected backups with the ability to configure several independent retention periods. Learn more about GFS in the Long-Term Retention Policy (GFS) section of the Veeam documentation.

GFS requires regular generation of full backups. For this, the backup method is changed to the Forward Incremental Method, which increases storage consumption. Learn more about backup methods in the Backup Methods section of the Veeam documentation.

You can change the backup method:

  • for all jobs (including new ones). GFS parameters for each job are configured individually;
  • for individual jobs. GFS parameters can only be configured or changed via a ticket.

For long-term storage without changing the backup method, you can manually configure individual jobs to store weekly and monthly backups. Each backup chain will consist of a full backup and additional incremental backups.

Enable archive storage for all jobs

  1. Create a ticket. In the ticket, specify:

    • which jobs to enable GFS for: all jobs (including new ones);
    • full backup type: Active or Synthetic;
    • the day of the week on which the full backup will be created.

  2. Once archive storage is enabled, we will notify you in the ticket.

  3. On the Veeam® Backup Enterprise Manager portal, when creating or editing a job open the Job Settings.

  4. Select the Keep certain full backups longer for archival purposes.

  5. Click Configure.

  6. Select the required archive copy creation rules and configure their parameters. You can set up multiple rules.

  7. Click OK.

Enable archive storage for individual jobs

Archive storage will be configured by technical support for the selected jobs. Archive storage parameters for new jobs or changes to existing storage parameters can only be handled via a ticket.

Create a ticket. In the ticket, specify:

  • full backup type: Active or Synthetic;
  • the day of the week on which the full backup will be created;
  • the jobs for which archive storage should be configured;
  • for each job: which rules and with what parameters to use for archive storage.

Archive copy creation rules

DescriptionParameters
Keep yearly full backupsEvery year, one of the copies will become an archive copy and will be kept for the specified number of years
  • Number of years to store the archive copy;
  • month — the copy created in the specified month becomes the archive copy
Keep monthly full backupsEvery month, one of the copies will become an archive copy and will be kept for the specified number of months
  • Number of months to store the archive copy;
  • week of the month — the copy created in the specified week of the month becomes the archive copy: the first (First) or the last (Last)
Keep weekly full backupsEvery week, one of the copies will become an archive copy and will be kept for the specified number of weeks
  • Number of weeks to store the archive copy;
  • day of the week — if several backups were created during the week, the copy for this day of the week becomes the archive copy