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

Updated Manual (markdown)

Dan MacDonald
2023-10-15 20:56:08 +01:00
parent a1ab35d059
commit 06d0bb1485
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Manual.md

@ -84,7 +84,7 @@ Snapshotting can be skipped with `--no-snapshot`.
### Snapshot format ### Snapshot format
The snapshots are all created using a specific naming format. This includes a timestamp that zfs-autobackup uses to determine when a snapshot can be destroyed by the [Thinner](Thinner). Snapshots are created using a specific naming format. This includes a timestamp that zfs-autobackup uses to determine when a snapshot can be destroyed by the [Thinner](Thinner).
It is possible to change this format by using `--snapshot-format`. Other snapshots that do not match this format are normally ignored by zfs-autobackup. Use `--utc` to use UTC for timestamps. It is possible to change this format by using `--snapshot-format`. Other snapshots that do not match this format are normally ignored by zfs-autobackup. Use `--utc` to use UTC for timestamps.
@ -97,8 +97,8 @@ More info [here](PrePost).
### Skipping conditions ### Skipping conditions
Snapshot creation for can be skipped for a dataset, under certain conditions: Snapshot creation can be skipped for a dataset, under certain conditions:
* `--min-change BYTES`: Only create snapshot if enough bytes are changed. (default 1) * `--min-change BYTES`: Only create snapshot if enough bytes have changed. (default 1)
* `--allow-empty`: If nothing has changed, still create empty snapshots. (Same as --min-change=0) * `--allow-empty`: If nothing has changed, still create empty snapshots. (Same as --min-change=0)
### Other options ### Other options