From 9baab01072832e2ebbf3af9abffe08ea115d4c8e Mon Sep 17 00:00:00 2001 From: DatuX Date: Wed, 23 Feb 2022 18:42:23 +0100 Subject: [PATCH] Updated Home (markdown) --- Home.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/Home.md b/Home.md index 13e54dc..f4359fe 100644 --- a/Home.md +++ b/Home.md @@ -177,11 +177,18 @@ So `rpool/data/vm100-disk-0` ends up as: `data/backup/pve01/rpool/data/vm-100-di Since its a backup, its usefull to preserve the original structure of the data like this. -#### Stripping the path +### Stripping the path Since you might think this is ugly, there is the `--strip-path` option. However this can lead to collisions if you 2 source datasets result in the same target paths. Since version 3.1.2 zfs-autobackup will check for this and emit an error. -Also if you later want to add datasets that are higher up the tree, you might run in to trouble. +#### Making source and target paths look the same + +If you want your source and target structure to look exactly the same, you have to do the following: + +* Select the whole source-pool. In this case: `zfs set autobackup:offsite1=true rpool` +* Use `--strip-path=1` +* Specify target-pool as target-path. In this case: `data` +* Use the `--force` option the first time to overwrite the existing target pool. (New in v3.1.2) ### Pull or push?