Typos

Dan MacDonald
2023-10-15 12:17:34 +01:00
parent 6d31c78808
commit e82799c410

@ -82,7 +82,7 @@ This allows the backup machine to login to `pve01` as root without password.
Next, we specify the filesystems we want to snapshot and replicate by assigning a unique group name to those filesystems.
Its important to choose a unique group name and to use the name consistently. (Advanced tip: If you have multiple sets of filesystems that you wish to backup differently, you may do this by creating multiple group names.)
It's important to choose a unique group name and to use the name consistently. (Advanced tip: If you have multiple sets of filesystems that you wish to backup differently, you may do this by creating multiple group names.)
In this example, we assign the group name `offsite1` to the filesystems we want to backup.
@ -183,15 +183,15 @@ Run the script on the backup machine and pull the data from the source machine s
### The results
As you might notice, zfs-autobackup preserve the whole parent-path of the source.
As you might notice, zfs-autobackup preserves 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.
Since it's a backup, it's useful 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.
Since you might think this is ugly, there is the `--strip-path` option. However this can lead to collisions if two source datasets result in the same target paths. Since version 3.1.2 zfs-autobackup will check for this and emit an error.
#### Making source and target paths look the same