mirror of https://github.com/jimsalterjrs/sanoid
Update sanoid.conf
keeps system from running sanoid on non existent datasets
This commit is contained in:
parent
9544ea7e6a
commit
2c3de61b2b
46
sanoid.conf
46
sanoid.conf
|
|
@ -3,29 +3,29 @@
|
|||
# It should go in /etc/sanoid. #
|
||||
######################################
|
||||
|
||||
# name your backup modules with the path to their ZFS dataset - no leading slash.
|
||||
[zpoolname/datasetname]
|
||||
# pick one or more templates - they're defined (and editable) below. Comma separated, processed in order.
|
||||
# in this example, template_demo's daily value overrides template_production's daily value.
|
||||
use_template = production,demo
|
||||
|
||||
# if you want to, you can override settings in the template directly inside module definitions like this.
|
||||
# in this example, we override the template to only keep 12 hourly and 1 monthly snapshot for this dataset.
|
||||
hourly = 12
|
||||
monthly = 1
|
||||
|
||||
# you can also handle datasets recursively.
|
||||
[zpoolname/parent]
|
||||
use_template = production
|
||||
recursive = yes
|
||||
# if you want sanoid to manage the child datasets but leave this one alone, set process_children_only.
|
||||
process_children_only = yes
|
||||
|
||||
# you can selectively override settings for child datasets which already fall under a recursive definition.
|
||||
[zpoolname/parent/child]
|
||||
# child datasets already initialized won't be wiped out, so if you use a new template, it will
|
||||
# only override the values already set by the parent template, not replace it completely.
|
||||
use_template = demo
|
||||
## name your backup modules with the path to their ZFS dataset - no leading slash.
|
||||
#[zpoolname/datasetname]
|
||||
# # pick one or more templates - they're defined (and editable) below. Comma separated, processed in order.
|
||||
# # in this example, template_demo's daily value overrides template_production's daily value.
|
||||
# use_template = production,demo
|
||||
#
|
||||
# # if you want to, you can override settings in the template directly inside module definitions like this.
|
||||
# # in this example, we override the template to only keep 12 hourly and 1 monthly snapshot for this dataset.
|
||||
# hourly = 12
|
||||
# monthly = 1
|
||||
#
|
||||
## you can also handle datasets recursively.
|
||||
#[zpoolname/parent]
|
||||
# use_template = production
|
||||
# recursive = yes
|
||||
# # if you want sanoid to manage the child datasets but leave this one alone, set process_children_only.
|
||||
# process_children_only = yes
|
||||
#
|
||||
## you can selectively override settings for child datasets which already fall under a recursive definition.
|
||||
#[zpoolname/parent/child]
|
||||
# # child datasets already initialized won't be wiped out, so if you use a new template, it will
|
||||
# # only override the values already set by the parent template, not replace it completely.
|
||||
# use_template = demo
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue