“Been there, seen that, done that” phrase is the most appropriate sense of accomplishment for any Moodle administrator who’s involved with Moodle migration and upgrade. The annual major releases from Moodle gives some sleepless nights to the Moodle developers to fix the issues which rise from improper Moodle migration. The following tips will allow the learning management to bite the bullet with confidence.

4 Handy Tips For Moving Moodle From One Server To Another

 

Moodle migration and moving the Moodle from one server to another does happen frequently. The reasons may involve security concerns, No official support from Moodle and most importantly leveraging the new functionalities provide by latest updates. The recent Moodle 2.6 release comes with some stunning new features for teachers, administrators and students. Moodle 2.6 SCORM has also been updated with extensive support. Moving Moodle from one server can also increase speed and performance if properly planned, which improves the scalability of Moodle to a new level. Although there are two ways of doing migration, the listed tips come in really handy and assist in a proper migration of Moodle on whole.

  1. Enable Maintenance Mode It is the first and foremost job that you don’t allow any one login during the migration. Setting up the Moodle site on maintenance mode prevents any new additions or modifications made to the Moodle database. Maintenance mode really comes in handy giving the administrator the option to leave the Moodle site inaccessible to the public while developing the site.  In general it is good for Moodle administrator to know how to access maintenance mode that can also be used when diagnosing problems within the Moodle site.
    Enable Maintenance Mode
  2. Backup Moodle databaseHaving Moodle backup everyday into a tape is a good practice. Not being able to back up important information of students, such as contacts, fee details and enrollments can have catastrophic results for learning management. Having backup in place can help in mitigating the loss of important information. As a standard process, it is in best interest for the learning management to have a backup and recovery systems as part of a disaster recovery plan Moodle migration. The following code below allows to back up the MySQL database. If you are not much into programming, you can follow simple steps listed here for backups created with mysqldump or phpMyAdmin.
    Backup Moodle database
  3. Copying Right DirectoriesIt is very essential to copy the MOODLEDATA folder from the previous install as a backup. Once the migration takes place we need to check the values in the code pointing towards to right directories. It is advised to upgrade from 1.9 – 2.1, then 2.2 to 2.5 followed by 2.6, it eliminates the files to be corrupted in the process of migration.
    Copying Right Directories
  4. Editing the Configuration files The last lap of moving Moodle from one server to another is crucial. Many important steps needs to be check listed and ticked ok before you proceed further. Most importantly moodledata permissions need to be reviewed and new server needs to be pointed towards the corresponding URL. Editing the config.php is the paramount of Moodle migration. Browse the code to find the config.php file and update details correctly, this is where most of the migrations fail.
    Editing the Configuration files