Skip to main content

Backup Verification (Platform Preparation)

Goal: confirm the Moodle template site on EL-CRON is working, up to date, and ready to be cloned for the new semester.

Template location

  • Web files: /elearning_data/template/{platformname}_template45 (EL-CRON 192.168.23.128)

  • Moodledata: /elearning_data/template/production_{platformname}_template45 (EL-CRON 192.168.23.128)

  • Database: production_{platformname}_template45 (192.168.23.167, Percona Server)

Steps

  1. Check template site is reachable

    • Access the template’s internal URL (mapped in DNS or /etc/hosts).

    • Log in as admin, go to Site administration → Notifications — there should be no unexpected upgrade prompts unless an update is required.

  2. Check if Moodle core is latest version

    • In the template site, go to Site administration → Notifications.

    • If a Moodle version update is available, update it now before cloning.

    • CLI option:

      /usr/local/lsws/lsphp82/bin/php /elearning_data/template/{platformname}_template45/admin/cli/checks.php

      (If you have a custom check script for version comparison)

  3. Check if all plugins are updated

    • Go to Site administration → Plugins → Plugins overview.

    • Update any plugins showing “Available update” before cloning.

    • CLI alternative (list outdated plugins if Moosh is available):


      moosh plugin-list --update

    • Test the site after updates to confirm no compatibility issues.

  4. Check template files on EL-CRON


ssh 192.168.23.128 'du -sh /elearning_data/template/{platformname}_template45' ssh 192.168.23.128 'du -sh /elearning_data/template/production_{platformname}_template45'

  • Ensure the size matches expectations and filedir, cache, sessions exist inside moodledata.

  1. Check template database exists and is responsive

mysql -h192.168.23.167 -uroot -p -e "SHOW DATABASES LIKE 'production_{platformname}_template45';" mysql -h192.168.23.167 -uroot -p -e "SELECT COUNT(*) FROM production_{platformname}_template45.mdl_user;"

 

  • The user count should be the template’s baseline (usually minimal test/admin accounts).

  1. Review OpenLiteSpeed logs for errors

ssh 192.168.23.128 'tail -n 100 /usr/local/lsws/logs/error.log'

  • No fatal errors should appear for the template site.

  1. Confirm template matches baseline configuration

    • Check course categories, theme, and settings match the standard for a fresh semester.

    • Make any baseline adjustments before copying to production.

✅ When to mark as ready:

  • Template site loads without errors.

  • Moodle is at the latest stable version.

  • All plugins are up to date.

  • Moodledata has the expected structure.

  • DB exists and is queryable.

  • No critical OpenLiteSpeed log errors.

  • Configuration matches the baseline for cloning.

Back to top