-
Notifications
You must be signed in to change notification settings - Fork 35
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
deleting from remote fails : has dependent clones #27
Comments
Hm there should not be any clones for snapshots you only sent to a backup location. I think the problem here is that you start sending and cleaning at the same time. pyznap will still be sending snapshots to your backup location, when the other instance already wants to delete snapshots. As sending is incremental, it depends on old snapshots to be there on the dest. So if you try to delete one such snapshot while it is sending, I guess it tells you that the snapshot has dependent clones (marked with the %recv). I would advise to always let
Like this the Also just a fyi, I don't know if this is by design: In you policy for your backup you don't specify any numbers for the snapshots to keep, so all of them will be set to 0. This means that all snapshots you send to your backup location will immediately be deleted again once you run |
Oke; this is the cron now : The initial issue is gone (you where correct) but its off by 1. There are 3 frequently, 7 hourly, 2 daily and 0 weekly 😄 Maybe I need more patience ? Anyways this can be closed, its clearly a configuration issue; thanks for the help! |
Well, you first clean snapshots on the backup dest, then send your new snapshots, meaning after that cron there will be more snapshots than specified in your policy :). If you always want to have the exact amount of snapshots as specified in your policy you need to do something like this:
This way it first takes snapshots, then sends them over to your backup, and then cleans old snapshots, meaning you are left with exactly the amount you specified. |
I logged the output for pyznap send & pyznap snap :
/etc/pyznap/pyznap.conf
the cron :
The idea is that we take snapshots local, make sure the data is backed up on the backup location. I must miss something but I'm unsure what?
The text was updated successfully, but these errors were encountered: