-
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
Does Not Perform Snapshot Cleanup #103
Comments
I had the same problem, until I realized I was only pulling with 'send' and not doing the cleanup with 'snap --clean'. They have to be done separately. At least that was my problem when I did a new install after a long time. |
This does not resolve the issue unfortunately. I got a 200GB container eating 2TB because it hasn't cleaned anything up in the last 9 months. |
To clarify, I want it to cleanup the snapshots on the local pool before sending. |
It just dawned on me what the issue was. In the config file, if comments proceed the parameters value, it does not get parsed correctly. These config file parsing bugs create some real gotchas and need to be resolved ASAP. Valid:
Invalid:
|
On a Proxmox install of mine, pyznap is not removing the old snapshots, even though
clean = yes
is specified in the config file.Below is what I mean by very old snapshots. I would like to only keep the snapshots as mentioned in the schedule.
The text was updated successfully, but these errors were encountered: