Repository navigation
Replies: 4 comments
|
Nope sorry: the datasets that dont have a common snapshot need to be destroyed on the target and resent. Holds are specifically ment to prevent this problem: You are allowed to delete all snapshots except the ons that are held, since these are the common snapshots. |
0 replies
|
Actually: you can delete the snapshots of the target dataset and use the -F option. This way you dont have to destroy any child datasets. |
0 replies
|
Ah, of course - thanks! I should've thought of this myself, really. |
0 replies
|
Version 4 can do this automatically when requested. :) (its still in early beta) |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hola,
I've been using zfs-autobackup for a while in various fashions, but recently upgraded my storage server so I can ship all my backups there without worrying about available space. So, trying to be smart, I set it up to
And since I sometimes find myself in urgent need to free up space, I used --no-holds to make my life easier when those situations hit.
Well, duh. Shouldn't be doing that, I suppose. Now I've got a lot of
FAILED: Cant find common snapshot with target.mostly for empty or near-empty datasets.
So my question becomes: Is there any way to recover from this situation, without having to start from scratch (move/delete remote datasets, send everything again)?
Thanks, and with embarrassed regards,
/Eirik
All reactions