Alain Raap

Hi Visvanath,

Our reason to move the automated backup to the database server was the NFS share we use to connect to our database server.
Once we moved the automated backup to the database server it ran much faster and more stable. If you have Moodle on one server,
you could also try to run the automated backup outside the Moodle cron with a bash script that is started by the Linux cron. Our
automated backup runs at night until the early morning.

An important issue I want to share here, it's not enough to only install a Moodle instance on your backup server!!! We found out that our automated backups
were incomplete when restored in the Moodle web application. It is also necessary to upload all the custom plugins and your own theme to the backup server.
We've tested this in our production-like environment and after this change we could restore the complete courses again.

Shelly I’m glad your problem is solved, btw we share (nearly) the same server configuration, feel free to have a chat to exchange experiences. We use MariaDB
for the database.

Shelly, there is an open Moodle Tracker about a quiz performance issue, don't know if this could point you in a good direction: https://tracker.moodle.org/browse/MDL-66199?jql=project%20%3D%20MDL%20AND%20component%20%3D%20Performance

How did you test the performance, how large is your database (in memory?) and do you use a caching server like Redis or Memcache?

Juan, I've got it working too, with the permissions 666 on the Redis socket it worked for me. I also had to make a Selinux policy to be able to connect to the Redis socket, this was denied by Selinux. Thanks for your advice.