DatuX

yep, no if it works then keep it that way :)

the plan was to finish 3.1.x features first before new big changes, but this is more important. (and shouldnt be that difficult after some refactoring)

the alpha2 version in git is working, needs some debugging and tuning. (e.g. cleanups on ctrl-c are still messy and can leave stuff mounted/cloned)

If created a tool to generate the actual checksums: https://github.com/psy0rz/zfs_autobackup/wiki/zfs-check zfs-autoverify will then use this tool to compare checksums. In the main time you can use zfs-check manually to check...

This is non-trivial to implement in a clean way. Perhaps it would help if you specify a faster cipher like arcfour in ~/.ssh/config. (https://github.com/psy0rz/zfs_autobackup#specifying-ssh-port-or-options) (If you're a company and want...

this has become more trivial with the latest changes. If any one wants this, vote it up and i might add it.

yes, because of the process handling extensions made for zfs-autoverify, this should be doable. however, are socat and spiped with encryption faster than regular ssh pipes? (i understand direct mbuffer...

it might even already be doable via --send-pipe and --recv-pipe, but maybe hackish and problematic with buildup/teardown. mbuffer is universally supported in operating systems. but we can support multiple tools.

awesome, thanks for the info!

ssh is pretty ok nowadays. :)