ansible-edda/playbooks/roles/backups/snapshots/setup/files/sanoid-templates.conf

60 lines
2.1 KiB
Plaintext

# Template for system datasets that are not being backed up anywhere. Snapshots are used to provide
# option for rollback without having to reinstall entire system. If the hardware crashes or becomes
# corrupt reinstalling might be smarter given the fact that hardware will likely be different.
[template_system]
frequently = 0
hourly = 36
daily = 30
monthly = 3
yearly = 0
autosnap = yes
autoprune = yes
# Template for home directories which will use the system template, but they don't change so fast.
[template_home]
hourly = 0
# Template for datasets with production data. Unlike system datasets, production datasets are
# expected to be backed up, both to spare local storage as well as a remote location. Therefore,
# snapshots only serve the purpose of providing snapshots for these backups. Otherwise, don't keep
# snapshots as they will just take up space. Applications that need their data versioned will be
# versioning themselves so they only need backups.
[template_production]
frequently = 0
hourly = 2
daily = 2
monthly = 0
yearly = 0
autosnap = yes
autoprune = yes
# Template for backup datasets which also doubles as a hot spare. The assumption is that these
# backup production datasets. In addition to three months of snapshots, keep 36 hourly snapshots for
# quick rollback in case of trouble. No monthly snapshots are kept as that would require the
# production template to produce them.
[template_backup]
autoprune = yes
frequently = 0
hourly = 36
daily = 90
monthly = 0
yearly = 0
### don't take new snapshots - snapshots on backup
### datasets are replicated in from source, not
### generated locally
autosnap = no
### monitor hourlies and dailies, but don't warn or
### crit until they're over 48h old, since replication
### is typically daily only
hourly_warn = 2880
hourly_crit = 3600
daily_warn = 48
daily_crit = 60
[template_ignore]
autoprune = no
autosnap = no
monitor = no