ambiser
/
btrbk
mirror of https://github.com/digint/btrbk
9
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

documentation: mention up-to-date status

lsbtr-related
Axel Burri 2020-08-20 18:53:46 +02:00
parent 12d80ee30b
commit 2f7e79ace6
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/btrbk.conf.5.asciidoc
View File

@ -140,15 +140,16 @@ Note that using ``long-iso'' has implications on the scheduling, see
*snapshot_create* always|onchange|ondemand|no::
If set to ``always'', snapshots are always created. If set to
``onchange'', snapshots are only created if the source subvolume
has changed since the last snapshot (more precisely: if the btrfs
generation has been increased since the last snapshot). If set to
``ondemand'', snapshots are only created if at least one target
subvolume is reachable (useful if you are tight on disk space and
you only need btrbk for backups to an external disk which is not
always connected). If set to ``no'', the snapshots are never
created (useful if another instance of btrbk is taking care of
snapshot creation). Defaults to ``always''.
``onchange'', snapshots are only created if the last snapshot is
not up-to-date, i.e. the source subvolume has changed (more
precisely: the btrfs generation has been increased) since the last
snapshot was created. If set to ``ondemand'', snapshots are only
created if at least one target subvolume is reachable (useful if
you are tight on disk space and you only need btrbk for backups to
an external disk which is not always connected). If set to ``no'',
the snapshots are never created (useful if another instance of
btrbk is taking care of snapshot creation). Defaults to
``always''.
*incremental* yes|no|strict::
If set, incremental backups are created. If set to ``strict'',