Running version 2.4.5. Automated backups scheduled to run at 3 AM on Tues and Fri. to a different server. Backup reports indicate backups successful after approx 1.5 hours. Yet ... seeing strange activity in db where mdl_backup_courses is being updated continuously for more than 5 hours after backup has completed. (see screenshot). This is slowing our system down to a halt. The queries indicate that moodle is updating a prior backup that was last backed up approx 2 months ago, and had an error status of 3. The update is setting the next backup to occur for the next schedule backup date. This seems logical given we didn't have the automated backup process running for a while during the summer and changed the parameters from storing the backup to the course area to a different server... however, why is this happening hours after a backup completes? And why does this particular process seem to slow our system down to a halt? Does it have to do with the fact that the backups are on a different server? That would explain it I suppose, however, the fact that the backup report indicates it was completed successfully after 1.5 hours while churning out queries hours and hours after the fact still concerns me. Just wondering if this is normal....
The queries are being executed in a timely manner but during normal activity the mysql screen never looks this full. (see screenshot) Our dba confirms adequate resources on the DB as well, our infrastructure staff confirm system resources (cpu, memory, etc.) are adequate. (VM) Normally, the performance is quite good.
Has anyone seen this behavior and/or have any suggestions as to how to fix? (this thread was started in the hardware/performance forum but when I confirmed it was the automated backup process causing the problems I thought it might be good to post here as well?)
