From 0972c5ea324aa0d7ba8995519c4d958f2d522777 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Kula?= <148193449+miku-orb@users.noreply.github.com> Date: Mon, 9 Mar 2026 15:38:15 +0100 Subject: [PATCH 2/3] Bug 42028: tweak default koha-run-backups settings "Configuration" tar file should not be so outrageously big (~10x bigger than the database, what in the world!). The biggest offender is the Zebra index files. These should not be backed up at all, instead regenerate them after restoring backup. There's no consistency between SQL and index dumps, they're not atomic, so restoring them like that is unsafe anyway. In fact, ideally that option should be removed completely so that nobody can shoot their foot off. Logs these days can also grow quite big with all these crazy AI crawlers out there nowadays and default retention settings. I don't think making N copies of the very same logs on the server, which are meant to be ultimately ephemeral anyways, is really beneficial... And now that we shrunk the needed storage by ~10x (YMMV), bump default 2 days to 7, making it much more likely you'll have old enough point of reference in case anything goes wrong with your Koha, before it gets nuked forever. --- debian/koha-common.cron.daily | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/koha-common.cron.daily b/debian/koha-common.cron.daily index 134858f4a3..68e1cce707 100644 --- a/debian/koha-common.cron.daily +++ b/debian/koha-common.cron.daily @@ -15,7 +15,7 @@ # You should have received a copy of the GNU General Public License # along with this program. If not, see . -koha-run-backups --days 2 --output /var/spool/koha +koha-run-backups --days 7 --exclude-indexes --exclude-logs --output /var/spool/koha #koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/archive_purchase_suggestions.pl -c --age=years:1 koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/automatic_renewals.pl -c koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/automatic_checkin.pl -- 2.53.0