yboetz
commented
1 year ago There is currently no way to avoid this. pyznap send will send all snapshots, you cannot exclude hourly/frequent ones. So send will always send those and snap will immediately delete them again. I have the same setup and just let pyznap delete the hourly/frequent ones again, it only happens once per day.
To avoid this the only option is to always keep the same/more snapshots on the dest than on the source, so also keep frequent and hourly ones on your backup. There's no disadvantage to that, zfs can handle a large amount of snapshots.
You don't need to keep 48 hourly snapshots though, since if you miss one backup it can always do incremental backup from the last daily one instead of a hourly.
jcferretti
First, let me say thanks for a great tool.
I run
pyznap senddaily andpyznap snapevery 15 minutes via crontab. I do not want to keep snapshots more frequent than daily in the destination for send (eg, no frequent, no hourly). I do want frequent and hourly snapshots in the source dataset; this seems consistent with intended usage, since a daily send is suggested and keeping enough hourlies to be able to survive some missed schedule would be tough (eg, would need 48 or more dailies so that there is a snapshot if one daily send is missed).Anyway, my issue is that
pyznap sendseems to send /all/ snapshots, including frequent and hourly, only for the nextpyznap snapto remove them:My configuration: