For Automated Course Backups there is a setting that tells the system not to back up a course that hasn't "modified" within a given period of time. What events cause a course to be flagged as modified for the purposes of the automated backups?
I updated to Moodle 3.4 on December 21st and there was a sudden increase in the number of courses that were being backed-up. I thought that something in the new code caused the issue so I set the system not to back up any courses that hadn't been modified within the past 7 days but that hasn't helped and it is quickly eating up disk space.
We have 216 courses on the system but not all of them are in use. For the past several months the system was backing up 25 courses and skipping the rest. On the day after the upgrade to Moodle 3.4 it backed up 94 courses and it has been doing that ever since.
I timed the upgrade to occur during the university’s winter break while the students were gone and most of the faculty was on holiday. I can imagine some activity to prepare for the winter quarter but not effecting so many courses and not all at once.
There are strategies that I can use to reduce the disk space consumption such as reducing the number of backups for a given course and shortening the time period before the system begins to delete old backups but I don’t understand why my current strategy is suddenly failing to produce the expected results.
Moodle 3.4 running on a virtualized server with CentOS (current version) as the OS.
Automated backups enabled to run on Sun, Mon, Wed and Fri mornings.
Saved to a specified directory
Maximum number of backups kept: 40
Delete backups older than: 120 days
Minimum number of backups kept: 1
Skip courses not modified since: 7 days