We migrated to Moodle 3.9 this week (from Moodle 3.5.x) and the automated backup ran for the first time yesterday. We have more than 5500 courses and normally we have between 300-500 backups each day. Yesterday, the first backup made 2130 backups (in 6 hours time), and that's really very fast.
Is it normal that the first time so many courses are backup'ed? And who has the same experiences with the (very much better) performance of this task? I excluded our largest course from the automated backup, this course runs only in the weekend because of the long time it runs (12 hours). I'm curious how long it'll run this weekend.
Alain Raap
Posts made by Alain Raap
We migrated this week from Moodle 3.5.x to Moodle 3.9 and that was a large upgrade for our Moodle site. All went smooth and we made some changes to the upgrade procedure of Moodle and the plugins. Just to share some experiences I'll explain how we did the migration:
- first we upgraded our database to the desired version for Moodle 3.9
- we copied all the plugins and the theme that needed an upgrade to the (web)server
- on the webserver we ran the cli upgrade php script of Moodle, this script also upgraded all the changed plugins and the theme
- advantage is that we don't get timeouts anymore while upgrading plugins from the web-interface, so run the plugin and theme upgrades on the server instead of via the admin web-interface
- our automated backup runs much faster now, we had a first backup run of 2130 courses that took about 6 hours during night
For our maintenance tasks we use Redhat Ansible Tower playbooks and Redhad satellite for software distribution and that works great.
Moodle in English -> Hardware and performance -> Moodle 3.9 Performance -> Re: Fresh Moodle 3.9 takes few seconds to open any page
by Alain Raap -
We had experience with moodledata/filedir on NFS, it's difficult to tune and to get a fast and reliable connection with the NFS server. We also had a problem with an antivirus program installed that hang up our server (with NFS server) with kerneltimeouts at random moments, so be aware of that if you choose for NFS as a solution. I posted some messages in the forums here about how we configured the NFS share, that was fast enough for us: https://moodle.org/mod/forum/discuss.php?d=362709&mode=3
Moodle in English -> Hardware and performance -> A new "Large scale Moodle deployment" support group -> Re: A new "Large scale Moodle deployment" support group
by Alain Raap -
Nadav, I understand Visvanath's remarks about the Telegram group, I also am very interested in large scale Moodle deployments and I don't use Telegram, so I'm already excluded from interesting information. Why not share your best-practices on this subject here in this forum? Or is this already shared somewhere?
Indeed digital learning is growing very fast (the number of students and courses) and also scalability and performance is an important issue. How fast can you adapt change when your Moodle site is growing faster than your IT department or sysadmins can handle? Maybe an interesting discussion how to handle these subjects in this fast changing world?
Indeed digital learning is growing very fast (the number of students and courses) and also scalability and performance is an important issue. How fast can you adapt change when your Moodle site is growing faster than your IT department or sysadmins can handle? Maybe an interesting discussion how to handle these subjects in this fast changing world?
Moodle in English -> Backup and restore -> [3.9.1] Delete oldest automated backup from Moodledata instantly, not keeping them in trashdir -> Re: [3.9.1] Delete oldest automated backup from Moodledata instantly, not keeping them in trashdir
by Alain Raap -
Hi Marius,
Where do you keep your backups from the automated backup? We store them in a different path outside the Moodle data. When our backups are removed (replaced with a new version), they are deleted from the filesystem only, and don't stay in the Moodle trashcan.
Where do you keep your backups from the automated backup? We store them in a different path outside the Moodle data. When our backups are removed (replaced with a new version), they are deleted from the filesystem only, and don't stay in the Moodle trashcan.