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

documentation: btrbk.conf.5: clarify behavior of 'snapshot_create ondemand' when there are multiple targets

prune-ignore-latest-common
Paride Legovini 2018-07-29 18:16:10 +02:00 committed by Axel Burri
parent 0d124a4373
commit 3dc06c8067
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

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