update

Edwin Eefting
2022-01-06 23:31:37 +01:00
parent 606527b53f
commit 808f243b1d
3 changed files with 14 additions and 2 deletions

@ -25,3 +25,7 @@ Try using something like: --filter-properties xattr or --ignore-transfer-errors.
This happens if you transfer between different Operating systems/zfs versions or feature sets.
Try using the --ignore-transfer-errors option. This will ignore the error. It will still check if the snapshot is actually received correctly.
> cannot receive incremental stream: kernel modules must be upgraded to receive this stream.
This happens if you forget to use --encrypt, while the target datasets are already encrypted. (Very strange error message indeed)

@ -1,6 +1,6 @@
# How zfs-autobackup handles encryption
How does zfs-autobackup handle encryption?
In normal operation datasets are transferred unaltered:
In normal operation, datasets are transferred unaltered:
* Source datasets that are encrypted will be send over as such and stay encrypted at the target side. (In ZFS this is called raw-mode) You dont need keys at the target side if you dont want to access the data.
* Source datasets that are plain will stay that way on the target. (Even if the specified target-path IS encrypted.)

8
_Sidebar.md Normal file

@ -0,0 +1,8 @@
zfs-autobackup:
* [Getting started](Home.md)
* [Performance tips (recommended)](Performance%20tips.md)
* [Common problems and errors](Common%20problems.md)
* [Thinning out obsolete snapshots](Thinner.md)
* [Handling ZFS encryption](Encryption.md)
* [Transfer buffering, compression and rate limiting.](Transfer%20buffering,%20compression%20and%20rate%20limiting.md)
* [Custom Pre- and post-snapshot commands](Pre%20and%20post%20snapshot%20commands.md)