I felt I should come back to the top and add this disclaimer. I am always talking about automated backups. I know I sometimes refer to it as backup in my description of the issue, but please know that I always mean automated backup.
Experienced a hardware failure during an automated backup. After getting everything put back together, I cleared out the backup folder to get fresh course backups however all courses that were skipped during the last successful backup were not created in the post hardware failure backups even though they don’t exist.
The backup email digest sent before the hardware failure and the one sent after the server was operational again were identical:
Automated backup pending: 0
Backup completed successfully
I ran select * from moodle.mdl_backup_courses; in MySQL and found that every course that wouldn’t create a new backup had a “laststatus” of 3. Do I need to go through and change them to a different status to get them back on track? Or can I truncate the mdl_backup_courses table to get all fresh backups? Any of the other backup tables, mdl_backup_controllers or mdl_backup_logs, need attention?
I am not sure if this is a similar, but this user had a status stuck in Running and it was recommended to truncate the backup tables:
and follow up here: