Bug 23943

Summary: koha-run-backups --days is misleading
Product: Koha Reporter: Magnus Enger <magnus>
Component: PackagingAssignee: Bugs List <koha-bugs>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: trivial    
Priority: P5 - low CC: aleisha, mirko
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30627
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Magnus Enger 2019-11-01 08:32:46 UTC
The documentation for the --days option to koha-run-backups says:

    --days:     the number of days to keep backups around for (default: 2)

Sometimes I do the following: 

1. Rename a backupfile, e.g. from instance-2019-10-22.sql.gz to instance-2019-10-22-1230.sql.gz
2. Run koha-dump to create a new instance-2019-10-22.sql.gz

This reveals that --days does not really care about days at all, just the number of files in the backup dir. This means that if I have adjusted the cronjob to keep backups for 14 days, after the next time it runs, I actually have backups for 13 days.
Comment 1 Aleisha Amohia 2024-04-02 03:02:05 UTC

*** This bug has been marked as a duplicate of bug 30627 ***