TIMELINE_LIMIT_YEARLY="10"
This example conguration enables hourly screenshots which are automatically
cleaned up. TIMELINE_MIN_AGE and TIMELINE_LIMIT_* are always eval-
uated both. In this example, the minimum age of a snapshot, before it can be
deleted is set to 30 minutes (1800 seconds). Since we create hourly snapshots, this
ensures that only the latest snapshots are kept. If TIMELINE_LIMIT_DAILY is
set to not zero, this means that the rst screenshot of the day is kept, too.
Snapshots to be Kept
• Hourly: The last ten snapshots that have been made
• Daily: The rst daily snapshot that has been made is kept for the last ten
days.
• Monthly: The rst snapshot made on the last day of the month is kept for
the last ten months.
• Yearly: The rst snapshot made on Dec 31st is kept for the last ten years.
4.7 Limitations
Although being ready for production, Btrfs as well as Snapper are constantly devel-
oped further. The following limitations exist at the moment. It is planned to solve these
issues in future releases.
4.7.1 Data Consistency
There is no mechanism to ensure data consistency when creating snapshot. Whenever
a le is written (e.g. a database) at the same time the snapshot is created, it will result
in a broken or partly written le. Restoring such a le will cause problems. Therefore
it is strongly recommended to always closely review the list of changed les and their
diffs. Only restore les that really need to belonging to the action you want to roll back.
Snapshots/Rollback with Snapper 111
