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

Updated Home (markdown)

DatuX
2022-02-23 18:02:09 +01:00
parent 5ace351b03
commit 52b3890280
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Home.md

@ -169,6 +169,22 @@ Run the script on the backup machine and pull the data from the source machine s
#### All operations completed successfully #### All operations completed successfully
``` ```
### The results
As you might notice, zfs-autobackup preserve the whole parent-path of the source.
So `rpool/data/vm100-disk-0` ends up as: `data/backup/pve01/rpool/data/vm-100-disk-0`
Since its a backup, its usefull to preserve the original structure of the data like this.
#### 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.
### Pull or push?
Note that this is called a "pull" backup. The backup (target) machine pulls the backup from the source machine. This is usually the preferred way. Note that this is called a "pull" backup. The backup (target) machine pulls the backup from the source machine. This is usually the preferred way.
It is also possible to let a source machine push its backup to the target machine. There are security implications to both approaches, as follows: It is also possible to let a source machine push its backup to the target machine. There are security implications to both approaches, as follows: