In for a penny ... in for pound ... followup ... more stuff related.
An Async Backup email message looks like this:
(very small site example)
Summary
==================================================
Courses: 6
OK: 3
Skipped: 3
Error: 0
Unfinished: 0
Course backup ad hoc task pending: 0
Warning: 0
Automated backup pending: 0
Backup completed successfully
It is sent after it completes.
There are thresholds on when to backup ... if a course hasn't had any changes, it's skipped. As you can see above, there were 3 courses in the above example that were skipped. I have mine set to keep only one ... not multiples.
Also, if you note, a backup process could extend beyond the allotted time limit and be tagged as pending which puts into adhoc_task. adoc_task executes later.
Also, there is a setting for auto as to where to save the backups.
Default is to save them in the sea of files of moodledata/filedir/
which means they can only be seen in Moodle GUI.
I prefer to be able to see those files:
In Auto backup setup, I have 'Specified directory for automated backups' set to a directory on a large mounted data disk.
We also don't know if all of your courses can be backed up!!!
Look in /moodledata/temp/backup/
If all courses are being backed up successfully, there will be 0 byte size log files in there. if you see any long named directories, something like; afwrwjadweraweadgsdksds those are either directories being used to build a backup file OR directories where the backup
failed. Been my experience that some large courses might fail at the very end of the process where process is to *copy* the backup.mbz file in there to it's desintation as per settings. If in any of those long directories, you find a moodle_backup.xml and a backup.mbz file, that's a valid/good backup, that, for some reason, could not be copied to destination.
Now here is something strange .. in task list
Automated backups report \core\task\automated_backup_report_task
Last run: Tuesday, 12 August 2025, 12:08 PM
Next run: Tuesday, 12 August 2025, 12:09 PM
That's the report. But ...
Automated backups \core\task\automated_backup_task
The actual process
Last run: Tuesday, 12 August 2025, 11:50 AM
Next run: Tuesday, 12 August 2025, 12:50 PM
You can see the report is actually before the running????!!!???
'SoS', Ken