-
Notifications
You must be signed in to change notification settings - Fork 51
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
[Feature request] Protect last x
number of snapshots
#20
Comments
And also to make sure that there is always a remaining copy on the remote host if this is needed (i.e. because I'm paranoid) |
👍 i'm all for adding a protect feature. @joltcan that is a good idea but anything remote is outside the scope of what |
Forget the remote part, that is only one use-case. Regardless I would prefer being able to have X copies left as a failsafe. |
Additional vote (as if required) for protect option. I am a newb with ZFS and am simultaneously in awe of the benefits it brings and abject terror at the ease with which data can be lost by the user doing something they really don't fully understand :-) |
+1 this should also be the default (never delete ALL snapshots, keep the latest, so you can do differential backups). If you really want to delete all of them use a flag like -f. |
When using syncoid, or other send-based backup solution, the last snapshot is used to calculate the delta to send an incremental stream. Using your script in that application would run the risk of destroying snapshots that zfs send/recv needs for incremental backup. It'd be nice if there was a feature to protect the last
x
number of snapshosts as to ensure their existence regardless of time cut-off point.The text was updated successfully, but these errors were encountered: