oetiker / znapzend

zfs backup with remote capabilities and mbuffer integration.
www.znapzend.org
GNU General Public License v3.0
608 stars 138 forks source link

Command to manualy initiate deleting of old snapshots (before sync round is complete) #422

Closed Harvie closed 3 years ago

Harvie commented 5 years ago

I had 3 weeks of downtime on my znapzend DST, so now everything is extremely slow, because there are lots of unsynced snapshots on SRC... Also i've started running out of space on SRC.

I think it would be nice if i could just manualy force it to sync the increment between oldest and newest snapshot, because after whole night of syncing the znapzend is still syncing the snapshots from the first day the DST died.

Also i think it would be usefull to be able to delete the snapshots from SRC immediately after the sync rather than at the end of the whole syncing round. Because i am starting to run tight on space, while syncing takes ages...

Harvie commented 5 years ago

sync the increment between oldest and newest snapshot

I've just realized this already happens. i was thinking that znapzends does zfs send -I for each snapshot separately... So this is good thing...

But what about the feature that would delete the SRC snapshot right after send/recv to DST? It will take some time before my pool is synced again and i could benefit from having some free space in the meantime...

I understand this might not be a good idea unless you have checked that the snapshot was really received and doing zfs list can be quite slow. So doing zfs list to check after each send/recv might be PITA... I certainly don't think this should be enabled by default...

Maybe just having separate command to initiate deletion of unneeded snapshots would be best option, so i can execute it before everything is synced, to reclaim at least some space if needed.

stale[bot] commented 3 years ago

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.

Harvie commented 3 years ago

bump

stale[bot] commented 3 years ago

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.