-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syncoid: sync incremental - hold selected snapshots during sync #924
Comments
@NicholasRush if a snapshot is being used in an ongoing send it can't be destroyed AFAIK and zfs will return an "busy" error. |
Can confirm; I've tested this extensively while making certain syncoid didn't have unexpected failure modes. If the snapshot is necessary for replication to continue, the destroy operation fails "snapshot busy". If the snapshot isn't necessary for replication to continue, the destroy operation succeeds. |
These comments are technically correct, but also kind of miss the point/problem here. Let's say I'm running syncoid and sanoid. I'm sending snapshots of a 40TB dataset. The delta between two monthly snapshots, June and July, is 10TB. The syncoid send process gets 8TB of the way through that 10TB, then... it fails. The network connection was interrupted. Sanoid will happily jump in and delete the June snapshot even though I ran syncoid with I'd love it if I had an option to make syncoid hold EACH base snapshot, and leave the holds present after it exits, and only remove them when the sync actually finishes. |
Hi there,
i have tested sanoid so much and it is a great tool, but there is a problem when it comes to
exclude
orinclude
snapshots. The problem is, that the incremental snapshots on the source could be delete through a snapshotengine during the sync. The best would be to hold all these snaps during the sync. If the sync is interrupted, it should check if theres a previous hold tag, finish the sync and remove all holds of the prevoious selected snapshots.The text was updated successfully, but these errors were encountered: