-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Explosion in backup file size #976
Comments
How large is the database file in the Also see #974 |
Right now
Also I made a backup yesterday afternoon and it was a "normal" 250MB vs the one in the morning being 4x the size?
Not sure what the temp file is either? |
I'm seeing the same here (the log file growth, not the temp file). |
+1 to this. 10GB db file and 4x 4GB plus backups. |
I'm working on it but need to wait for an update by the database programmers. You can try setting the retention time in the main config (enabled advanced options) to 0. This increases the risk of corrupted databases, though. I have no way of knowing by how much. If the database is corrupted you lose history and stats but no settings and can restore from the latest backup. |
It would also help to see the file listing of the content of one of the backup.zips. |
Earlier this week I noticed that the hydra2 web page was down and sonarr/radarr were complaining it wasn't available. I restarted the VM and shortly later sab notified me the disk was full. On further investigation I found what's in this picture. I cleaned out some of the larger big ones to get things running again.
I'm currently on 7.10.2 and I go in and hit update maybe once every couple weeks.
October backups seem reasonable, but something big happened in November.
nzbhydra-debuginfos-2024-12-06-09-51.zip
The text was updated successfully, but these errors were encountered: