by Marius S.
Hello Ken,
Administration -> Server -> Tasks -> Task processing all values are set to defaults. Scheduled task concurrency limit: 3, Scheduled task runner lifetime: 30min, Ad hoc task concurrency limit: 3, Ad hoc task runner lifetime: 30min.
If I go to Site administration -> Server -> Tasks -> Task logs and search for automated_backup_task Success and backup_cleanup_task Success
For both I get 24 lines and the Start time is almost the same, in some lines time is different in 1 minutes, but mostly it's the same Start time.
For both I get 24 lines and the Start time is almost the same, in some lines time is different in 1 minutes, but mostly it's the same Start time.
In moodledata/temp/backup currently there is 3500+ .log files from dates Aug 17th to Aug 24th. But all files are 0 byte size.
Also there is 12 directories with dates Aug 17 & Aug 23. Inside these directories there is xml files, and other folders like sections,course,files,activities.
Also there is 12 directories with dates Aug 17 & Aug 23. Inside these directories there is xml files, and other folders like sections,course,files,activities.
Yes, I understand that moodledata space usage if affected by assignments, teachers uploading new files/deleting old ones etc. But this is still strange because this never happened before and we had like 200-300GB free space and we didn't face this problem. Now we have 600GB free space and we ran out of space two times and both times was during weekly course backups in the weekend.
Semester is not even started so there is not much action in the Moodle system right now, so I highly doubt about teachers taking backups, uploading tons of files, etc.
Today in the morning weekly backups finished (as I deleted files manually from moodledata/trashdir so automated backups continued and finished this morning). So I checked on our Specific location where additional .mbz backups are create, so for this week it was 2370 courses and total .mbz backups size 248GB.
So I suppose in Moodledata backups takes similar size and oldest backups are deleted when new are created, so there should be no problems.. Maybe in Moodle 3.9 something changed in backups/deletion process?
Semester is not even started so there is not much action in the Moodle system right now, so I highly doubt about teachers taking backups, uploading tons of files, etc.
Today in the morning weekly backups finished (as I deleted files manually from moodledata/trashdir so automated backups continued and finished this morning). So I checked on our Specific location where additional .mbz backups are create, so for this week it was 2370 courses and total .mbz backups size 248GB.
So I suppose in Moodledata backups takes similar size and oldest backups are deleted when new are created, so there should be no problems.. Maybe in Moodle 3.9 something changed in backups/deletion process?
Thanks,
Marius.
Marius.