Alain Raap

Maybe you can test your database connection with this little script on your webserver. It returns the tables of your Moodle database.

Richard, does your automated backup makes 1300 backups in 2 hours? That's really fast! I also run the automated backup task outside Moodle and I have a separate logfile for this (Linux cron) task. So the whole automated backup run is logged in this logfile. Perhaps because of the adhoc task that is running the backups now that the mail isn't giving you a good insight in the results of the run?

I haven't tested with a large number of courses yet to check the performance of the automated backup task.
Our automated backup task takes about 10 hours to complete in the present Moodle version (3.5).
What I noticed is that when I added new courses to my new Moodle 3.9 environment, they weren't backup'ed
the same evening but they were scheduled for the backup run the next day.

Here I found a tracker about the adhoc task and the automated backup task:

https://tracker.moodle.org/browse/MDL-65729 in https://docs.moodle.org/dev/Moodle_3.9_release_notes

Hi Marius,

I'm also testing the automated backup process at the moment and you're right about the random creation of backups. I see these messages
in the automated backup log:

Putting backup of Startopleiding in adhoc task queue ...
complete - next execution: Thu, 10 Sep 2020 22:00:00 +0100
Putting backup of Communicatieve vaardigheden in adhoc task queue ...
complete - next execution: Thu, 10 Sep 2020 22:00:00 +0100

Adhoc task queue wasn't present in a previous version. Just as you mention, backups were made from increasing courseid 1 to last courseid