patrick/zfs_autobackup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update

Edwin Eefting
2022-01-07 14:21:42 +01:00
parent e0273933bc
commit 5ed9c7e06f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Thinner.md

@ -31,7 +31,7 @@ The format of the other rules is: `<Interval><TTL>`.
Since this might sound very complicated, the `--verbose` option will show you what it all means: Since this might sound very complicated, the `--verbose` option will show you what it all means:
```console ```console
[root@backup ~]# zfs-autobackup --verbose offsite1 --keep-source=10,1d1w,1w1m,1m1y [root@backup ~]# zfs-autobackup -v offsite1 --keep-source=10,1d1w,1w1m,1m1y
zfs-autobackup v3.1.1 - (c)2021 E.H.Eefting (edwin@datux.nl) zfs-autobackup v3.1.1 - (c)2021 E.H.Eefting (edwin@datux.nl)
Selecting dataset property : autobackup:offsite1 Selecting dataset property : autobackup:offsite1
@ -53,7 +53,7 @@ You can specify as many rules as you need. The order of the rules doesn't matter
Keep in mind its up to you to actually run zfs-autobackup often enough: If you want to keep hourly snapshots, you have to make sure you at least run it every hour. Keep in mind its up to you to actually run zfs-autobackup often enough: If you want to keep hourly snapshots, you have to make sure you at least run it every hour.
However, its no problem if you run it more or less often than that: The thinner will still keep an optimal set of snapshots to match your schedule as good as possible. However, its no problem if you run it more or less often than that: The thinner will still keep an optimal set of snapshots to match your schedule as close as possible.
If you want to keep as few snapshots as possible, just specify 0. (`--keep-source=0` for example) If you want to keep as few snapshots as possible, just specify 0. (`--keep-source=0` for example)