This summer we have updated from Moodle 3.3 to Moodle 3.5 and updated our Webserver.
We do weekly automatic backups by running php /admin/cli/automated_backups.php
We backup ~2500 courses to Moodledata and to separate folder, it takes 75-80hours to complete backup, total size ~100gb of .mbz files.
Could you please share your backup time?
I would like to know if this is normal time to backup higher amount of courses?
Because we have updated Moodle and Webserver in the summer when there was no load. Now there is 200-300+ students connected to Moodle all the time and automatic backup is running few days in a row, server load goes to 7.0-9.0 according to 'top' or 'htop' command.
During higher load most of the time 'mysqld' or automated_backups.php shows higher CPU% usage.
Here is load example:
We are not sure if automated backups are slowing down webserver or maybe Moodle 3.5 is slower or maybe we should optimize php/apache/mysql settings?
We use Database for Session Handing, should we consider disabling this option?
As default setting is Default: No
Our Webserver "hardware" is the same, it's VM with 8CPUs, 32GB RAM. We just updated to PHP7.1.20 (now using php-fpm), new version of mysql, I believe we have mariadb now, as I needed to change in config from mysqli to mariadb.