How to snapshot SRC frequently and send to DST infrequently? about znapzend HOT 3 CLOSED

it is planned to make znapzend cleverer concerning sending snapshots to destinations (e.g. sending only when necessary as you pointed out and sending only snapshots that 'belong' to znapzend)

from znapzend.

Cool.

I actually do use snapshots that don't "belong" to znapzend, essentially like this:

zfs snapshot pool/dataset@some-milestone
zfs bookmark pool/dataset@some-milestone pool/dataset#some-milestone
sleep 432000 # well, not literally
zfs destroy pool/dataset@some-milestone

The some-milestone snapshot gets copied over by znapzend and stays put. If there's ever some sort of problem (manual intervention, some extra cleanup script going mad when desperate to free up space on a small ssd-based pool, whatever) that causes there to be no snapshots in common between source and destination, recovering from a bookmark with

zfs send -i pool/dataset#some-milestone  pool/dataset@some-znapzend-snapshot | ... zfs recv -vuF remote/from_pool/dataset -vuF

is an easy enough fix.

I guess that's best done with a dataset property that indicates whether or not to send intermediate snapshots (including ones not owned by znapzend) on a dst-by-dst basis.

Orthogonally, any sort of "good enough" way to avoid waking up each dst much more frequently than "intA" (in "retA=>intA,retB=>intB,...") is probably fine, so I'm happy that it is planned. Have znapzendzetup throw a warning if the longest src ret=>int pair will roll away snapshots too soon for them to reliably get to all the dsts.

from znapzend.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from znapzend.