mirror of https://github.com/digint/btrbk
documentation: mention up-to-date status
parent
12d80ee30b
commit
2f7e79ace6
|
@ -140,15 +140,16 @@ Note that using ``long-iso'' has implications on the scheduling, see
|
||||||
|
|
||||||
*snapshot_create* always|onchange|ondemand|no::
|
*snapshot_create* always|onchange|ondemand|no::
|
||||||
If set to ``always'', snapshots are always created. If set to
|
If set to ``always'', snapshots are always created. If set to
|
||||||
``onchange'', snapshots are only created if the source subvolume
|
``onchange'', snapshots are only created if the last snapshot is
|
||||||
has changed since the last snapshot (more precisely: if the btrfs
|
not up-to-date, i.e. the source subvolume has changed (more
|
||||||
generation has been increased since the last snapshot). If set to
|
precisely: the btrfs generation has been increased) since the last
|
||||||
``ondemand'', snapshots are only created if at least one target
|
snapshot was created. If set to ``ondemand'', snapshots are only
|
||||||
subvolume is reachable (useful if you are tight on disk space and
|
created if at least one target subvolume is reachable (useful if
|
||||||
you only need btrbk for backups to an external disk which is not
|
you are tight on disk space and you only need btrbk for backups to
|
||||||
always connected). If set to ``no'', the snapshots are never
|
an external disk which is not always connected). If set to ``no'',
|
||||||
created (useful if another instance of btrbk is taking care of
|
the snapshots are never created (useful if another instance of
|
||||||
snapshot creation). Defaults to ``always''.
|
btrbk is taking care of 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'',
|
||||||
|
|
Loading…
Reference in New Issue