shuman wrote:Awesome! I'll give it a try. Are there any gotchas we should know about or any assumptions that might not be standard?
there are always some... but currently I don't know of anything what could cause loss of data. but if you would use the options like force overwrite, destroy remote (if needed) and fallback (from incr to full in case of missing source snapshot), I would try it first on a different setup with dry-run and debug log to screen. just to be sure what would happen.
there are so many possible combinations of exceptions and requirements during send and receive and actual status of filesystems and snapshots, that even the original SUNW package was just logging the problems and skipped operations, waiting for manual solving.
even the -R flag (replication) which is native to zfs send, won't work fully automatically for all combinations. the script can do that, but needs from you to be aware of it by using the various flags. you will see in the help. so won't do anything bad (syncing the state by destroy operations) without to be told in the forms of usage options.
the script is an official ubuntu package, although not merged to main repository yet. it needs to be mature and well tested before.