by Ken Task.
It's an automated process and will always take courses sequentially ... 1 through whatever CID is last. Having an issue with the front page backup (CID #1) could be problematic to the entire script.
The only reason I suggested manipulating the DB tables was the nextrun date had already past and meant it would never be run again. One should not resort to manipulating the DB to fix things ... last resort.
What I had to do with one system was truncate all the related tables .... by doing that, essentially, it was like Moodle had never run autobackups. All tables then would have new data (dates/status) from the time it was run. Then had to investigate individual courses that were problematic .... 96 Gig course, for example. After having done this, had no more problems with automated backups on that system.
I would think that course ID 1 (the front page) should be small in comparison to other courses and should complete every time.
So before assuming the worse let's see how it goes with the next run. ;)
'spirit of sharing', Ken