-
|
Lately, I've been unable to create a backup and update Medusa. I'm 100 commits behind. Running on TrueNAS server inside a Jail. I can watch the backup file grow in size, using FileZilla, on the server as I refresh the directory. The backup file size has reached 4,405,660,220. Is that too large for only 46 shows? Edit: I did look at the logs but didn't see any WARNINGS related to this.
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
|
Probaly your cache has grown large. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. And which cache file? Assuming I can delete it? I see the recommended file is big. Perhaps the culprit.
|
Beta Was this translation helpful? Give feedback.
-
|
Also, no option for advanced to not include cache.
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, delete the recommended file. |
Beta Was this translation helpful? Give feedback.
-
|
From next release the recommended.dbm file will not grow as fast. |
Beta Was this translation helpful? Give feedback.
-
|
I just noticed I have two Cache directories. The second is super old.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks all. Worked like a charm! |
Beta Was this translation helpful? Give feedback.
-
|
Drrr...found the advanced tab. Right in front of my eyes. 🤦♂️
|
Beta Was this translation helpful? Give feedback.
Probaly your cache has grown large.
Might want to also check your *.dbm files. Those can also have grown large. You can delete those, and restart medusa.
Last there is also an option to not include the cache files within the backup. In
config - Advanced settings - backup