mdl_backup_courses
laststatus field has number:
1 = OK
2 = unfinished
3 = skipped
query
select courseid,laststatus from mdl_backup_courses where laststatus=2
If you see an un-finished, check:
moodledata/backup/temp/ for any .log file that is larger than 0 bytes.
That log file might have info in it.
Also, if there is any 'contenthash' named directory (long string of letters/numbers)
inspect what it contains.
cd pathtomoodledata/backup/temp/[contenthash]
ls -l
IF you see a backup.mbz file therein it could be a good backup that
the operating system couldn't *copy* to destination which is a known issue
of OS's. In this case, the course would never be copied to the designated
destination NOR would it be in filedir.
One can, however, use the command line mv command to move the .mbz file
to the designated destination.
More than likely, in the directory where you find a backup.mbz there will also be
a moodle_backup.xml file. Use head -n 20 moodle_backup.xml to see the XML tag that
shows the filename Moodle would have used had it been able to complete the backup.
Had a server set to do autobackups that had a course that would not backup via cron job (auto) ... similar to your situation, I think. I finally had enough and truncated all the data in mdl_backup_courses. And the issue was resolved.
Will that work for you? Don't know for sure. This is one of those areas that is specific to individual servers ... ie, one solution not necessarily for all, me think.
'spirit of sharing', Ken