DatuX

True, this was originally to prevent people "shooting them self in the foot" and accidentally deleting the common snapshot. However in snapshot-mode this makes sense i guess. And even if...

hmm.. i realise that keep-target=0 also is usefull for onetime replication .

I've made some preparations for this. It will be called --keep-source=cleanup and --keep-target=cleanup, to indicate we really want a cleanup. E.g.: delete all snapshots belonging to this backup and breaking...

indeed..maybe the commandline specify the default and global settings, while properties can overrule some settings per dataset?

@Scrin yep i was thinking about that as well. perhaps this would take the form autobackup:offsite:min-change=1 ? or autobackup:offsite.min-change=1 ? i think the : is mean for namespace seperation, so...

i can also imagine setups that use autobackup:host.server.net=true ill check later what currently is allowed in zfsbackup and which snapshotnames are valid.

what about: autobackup:offsite@min-change=1

indeed..i thought i tried a property with an @ but apparently not.

sounds good, but call it --no-thinning-missing. and dont forget the "or --no-thinning", since that always should mean no thinning at all. this is also the reason i added progress reporting,...

in your case the slow part is that its getting a list of snapshots for every target dataset thats missing on the source. (and maybe it tries to get the...