Christoph Klaffl
Christoph Klaffl
This implements the desired feature to bypass ssh for sending the replication data and use a plain TCP connection. Added warnings of course that this option should not be used...
the following scenario will work with this PR: ``` zfs create pool/dataset zfs snapshot pool/dataset@duplicate syncoid pool/dataset pool/dataset2 zfs destroy pool/dataset@duplicate zfs snapshot pool/dataset@duplicate syncoid --force-delete pool/dataset pool/dataset2 ```
…rinting a warning Fixes #604
…t exist (and only skip child datasets which vanished) Fixes #754
previously the following scenario host1: pool1 --- syncoid over ssh ---> host2: pool1 host2: pool1 --- syncoid local --------> host2: backup/pool1 would fail if run concurrently, because the zfs receive...
this brings back the --no-rollback option without reverting to the old way of explicit rolling back the target filesystem. The option is very useful to others (https://www.reddit.com/r/zfs/comments/xcffnn/syncoid_norollback_option_gone/) and me.
Tested with: - ubuntu 22.04 - ubuntu 24.04 - debian 12 Fixes #921