docs: update Infrastructure/backup-infrastructure
This commit is contained in:
parent
736bdcd124
commit
ddc75bc6a6
1 changed files with 2 additions and 2 deletions
|
@ -2,7 +2,7 @@
|
||||||
title: Backup infrastructure
|
title: Backup infrastructure
|
||||||
description:
|
description:
|
||||||
published: true
|
published: true
|
||||||
date: 2025-02-15T21:59:27.423Z
|
date: 2025-02-15T22:03:47.122Z
|
||||||
tags:
|
tags:
|
||||||
editor: markdown
|
editor: markdown
|
||||||
dateCreated: 2025-02-15T21:28:29.716Z
|
dateCreated: 2025-02-15T21:28:29.716Z
|
||||||
|
@ -34,6 +34,6 @@ Then you can run `bacoid`
|
||||||
|
|
||||||
## Config notes
|
## Config notes
|
||||||
|
|
||||||
Since zfs config variables are recursive, settin syncoid:* config files on rpool will then mean that every volume will be backed up. To exclude a volume that you don't want backed up, you can set syncoid:pool_a and syncoid:pool_b as empty.
|
Since zfs config variables are recursive, setting syncoid:* config on rpool will then mean that every volume under it will be backed up. To exclude a volume that you don't want backed up, you can set syncoid:pool_a and syncoid:pool_b as empty.
|
||||||
|
|
||||||
Also, bacoid does not create a new snapshot when sending a backup. It thus relies on sanoid to create the snapshot, which are then sent with bacoid.
|
Also, bacoid does not create a new snapshot when sending a backup. It thus relies on sanoid to create the snapshot, which are then sent with bacoid.
|
Loading…
Add table
Reference in a new issue