Retention: how many versions are kept

Without a rule the backup directory keeps growing with every run until storage space runs short. The retention determines how many backups are kept; everything beyond that is deleted on the next run or at the push of a button.

What counts toward the limit

Only entries whose file really exists count toward the quota, as well as backups that after the upload only exist at the cloud provider. Entries without a file are taken out of the list as dead records, without using up the space of real backups. If a file cannot be deleted, its entry stays and the failure ends up in the log — an invisible file on the disk would be worse than one entry too many.

Setting the limit and cleaning up

1. The value is in “Kakapo Backup” on the left under “Configuration” in the item “Scope”.
2. In the “Retention” field, enter how many backups are kept; 1 to 60 are allowed, the default is 5.
3. At “Cleanup”, click “Clean up now” to apply the rule immediately.
4. The message names the number of backups removed; every operation is recorded in detail in the “Logs” (in German: „Protokolle“) area.

Protecting individual backups

• “Lock” in the backup list sets a deletion lock for a number of days, 30 is suggested; the retention never takes locked backups along
• “Unlock” only takes effect once the lock period has expired
• “Additionally keep monthly backups” in the “Schedule” (in German: „Zeitplan“) area protects the first backup of each calendar month via the “Keep months” field; 0 switches that off, 24 months is the maximum possible
• Backup profiles bring their own retention, which applies only to the backups of that profile