You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i have tested sanoid so much and it is a great tool, but there is a problem when it comes to exclude or include 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:
@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.
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: