From ddc75bc6a66ca4fbb99b8b9f91a8c866d4e4af6e Mon Sep 17 00:00:00 2001 From: Antoine Martin Date: Sat, 15 Feb 2025 22:03:49 +0000 Subject: [PATCH] docs: update Infrastructure/backup-infrastructure --- Infrastructure/backup-infrastructure.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Infrastructure/backup-infrastructure.md b/Infrastructure/backup-infrastructure.md index 5a71b6b..667b7a9 100644 --- a/Infrastructure/backup-infrastructure.md +++ b/Infrastructure/backup-infrastructure.md @@ -2,7 +2,7 @@ title: Backup infrastructure description: published: true -date: 2025-02-15T21:59:27.423Z +date: 2025-02-15T22:03:47.122Z tags: editor: markdown dateCreated: 2025-02-15T21:28:29.716Z @@ -34,6 +34,6 @@ Then you can run `bacoid` ## 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. \ No newline at end of file