Memory and storage are not the same thing. The error sounds like a memory issue, but deleting the files would only help for storage. Where I am, the Koha server runs as a VM, and we backup the entire VM nightly, so we are in a similar place regarding separate backups. However, these files can sometimes still be useful as a way to speed up recovery times. IIRC, there is a parameter somewhere, perhaps as an argument to the cron script, that tells it how many of these history files to keep. You might try reducing the number down to just 1 or 2, which is what we did. *Joel Coehoorn* Director of Information Technology *York University* Office: 402-363-5603 | jcoehoorn@york.edu | york.edu On Wed, Mar 22, 2023 at 8:39 AM Russel G. P. Shihepo <russellgeeps@gmail.com> wrote:

Hi everyone,

I have an issue with the db-dumps created by Koha into the /var/spool/koha {instance name} . It finishes my memory. I was wondering whether running a CRON tab to auto delete these files will cause any harm. We run our own backups every 24 hours, thus we do not need these files. And does the database depend on these caches and dumps?

Our koha is used to preserve African indigenous literature, and pre-colonial publications from the museum.

Thank you so much in advance.

Sincerely, Russel Shihepo Notitia Systems cc Namibia - Africa +264813223143 _______________________________________________

Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha