patrick/zfs_autobackup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated Home (markdown)

DatuX
2022-02-23 18:42:23 +01:00
parent 52b3890280
commit 9baab01072
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
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. 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. 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? ### Pull or push?