⁦B.⁩ Making backups

Choosing how many versions to keep

Why

With the “Dated versions (recommended)” layout, every backup creates a new version. Unchanged files do not take up space a second time, but changed ones do, so the history grows over time. Retention rules delete old versions by themselves.

Before you start

  • A deleted version is gone from the drive for good. If you need the state of a given day for years, record that version on a disc (see “Recording a backup version on a disc”).
  • The rules also delete versions timestamped with Sigelith, together with their seal.

Step by step

  1. On the “Backup” page, in the “Backup layout” box, find the “Keep:” field.
  2. Choose one of the options:
    • “all versions”: nothing is deleted. Then keep an eye on the free space on the backup drive;
    • “recent versions”: set a number next to it, for example 10. Older versions are deleted;
    • “calendar: days, weeks, months”: set three numbers next to it, for example 7 days, 4 weeks and 12 months. The newest version is kept from each of the last 7 days, 4 weeks and 12 months in which a backup was made. The history is dense for recent changes and sparse for old ones.
  3. Save the template again so that the rule also applies to backups from the template (see “Saving settings as a template”).

What you should see

Surplus versions disappear after the next successful backup. During the backup, the program then shows “Tidying up history” and the number of versions deleted.

What next

The program never deletes:

A backup that was interrupted or finished with errors deletes nothing.

If something goes wrong

  • The “Keep:” field is inactive: the backup uses the “Mirror copy” layout, which keeps only the current state.
  • Old versions do not go away: the rule only takes effect after a successful backup. Also check that the template was saved after the rule was changed.
  • Not enough space despite the rules: see “Not enough space on the backup drive”.