From 8a6c786871c75c625946345c5343788188b65557 Mon Sep 17 00:00:00 2001 From: DatuX Date: Fri, 19 Aug 2022 14:03:47 +0200 Subject: [PATCH] Updated Thinner (markdown) --- Thinner.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Thinner.md b/Thinner.md index 9459f20..c39bf0e 100644 --- a/Thinner.md +++ b/Thinner.md @@ -4,6 +4,8 @@ The thinner is the thing that destroys old snapshots on the source and target. The thinner operates "stateless": There is nothing in the name or properties of a snapshot that indicates how long it will be kept. Everytime zfs-autobackup runs, it will look at the timestamp of all the existing snapshots. From there it will determine which snapshots are obsolete according to your schedule. The advantage of this stateless system is that you can always change the schedule. +Another advantage is if your backup has failed for a longer time: It might have "missed" your monthly backup date, but the thinner then still holds the snapshot thats closest to the intended target date. + Note that the thinner will ONLY destroy snapshots that are matching the naming pattern of zfs-autobackup. If you use `--other-snapshots`, it wont destroy those snapshots after replicating them to the target. ## Thinning schedule