Moodle Course Copy, Backup, or Restore Not Working: Common Causes for Schools

Course copy, backup, and restore are some of the most useful Moodle tools for schools. They help administrators prepare new academic terms, duplicate course templates, move content between departments, preserve old course records, and recover materials when something goes wrong.

When these tools stop working, the impact can be frustrating. A teacher may not be able to copy last year’s course. A department may be waiting for a restored course shell. A school may discover that automated backups have been failing for weeks. In many cases, the problem is not caused by a single broken button. It is usually connected to Moodle cron, server limits, course size, permissions, plugins, or the way the course was built.

This article explains the most common reasons Moodle course copy, backup, or restore may fail for schools, and what administrators should check before the issue affects the next term.

I am Director of Rahab Ministry (a program of Youth Unlimited). We are impressed with Mindfield’s IT specialists in helping us redesign a website (Rahab.yugta.ca) and their ongoing support. They were responsive and helped us think ahead instead of waiting for us to tell them what needed to be done. We will continue to look forward to their support.

 

Joanna Yee

Director, Rahab Ministry.

review Source: Google Reviews

Outline

• • Moodle Cron or Background Tasks Are Not Running Properly

  • Course Files, Media, and Server Limits Are Too Large

  • Plugin, Theme, or Course Format Compatibility Issues

  • Moodle Version and Cross-Site Restore Problems

  • Permissions and User Data Can Make the Process More Complicated

  • Best Practices for Schools Before Copying or Restoring Courses

  • When Course Copy Problems Point to a Bigger Moodle Issue

  • Frequently Asked Questions(FAQs)

Moodle Cron or Background Tasks Are Not Running Properly

One of the first areas to check is Moodle cron. Cron runs many background processes in Moodle, including scheduled tasks and ad hoc tasks. These background tasks are important for course copy, backup, restore, notifications, automated backups, and other site processes.

When cron is not running correctly, schools may notice problems such as:

• Course copies stuck in progress
• Backup jobs that never finish
• Automated backups that do not run
• Restore tasks that appear incomplete
• Ad hoc tasks staying in the queue

This is especially important for Moodle sites using asynchronous backup and restore. Asynchronous processing allows users to continue working while Moodle handles backup or restore tasks in the background. However, if cron or ad hoc tasks are not processing correctly, these jobs may remain queued instead of completing.

For schools, this can become a major issue during the start of a semester or school year. Administrators may be copying many courses at the same time, while teachers are also preparing content. If Moodle’s background task system is not healthy, those course copy and restore processes can pile up quickly.

Schools should check whether cron is running regularly, whether scheduled tasks are overdue, and whether ad hoc tasks are stuck in the task queue. If Moodle course copy is stuck but the site otherwise appears to work, cron is still one of the first things to review.

Course Files, Media, and Server Limits Are Too Large

Plugin, Theme, or Course Format Compatibility Issues

Moodle courses often contain more than standard activities. A course may include third-party activity modules, custom blocks, special question types, filters, reports, course formats, certificate tools, attendance plugins, or theme-specific elements.

If a course depends on a plugin that is missing, outdated, disabled, or incompatible with the destination Moodle site, the copy or restore process may fail. In other cases, the restore may complete, but some activities may be missing, broken, or displayed incorrectly.

This is especially common when:

• A school restores a course from an older Moodle site into a newer one
• A course was created before a Moodle upgrade
• The destination site does not have the same plugins installed
• A course format or activity plugin is no longer supported
• Theme-specific layouts or blocks behave differently after restore

Theme-related issues can also affect how restored courses appear. The course content may technically restore, but blocks, layouts, section formats, or display settings may not behave as teachers expect.

Schools should check whether the source and destination Moodle sites have the same required plugins installed. They should also confirm that those plugins are compatible with the Moodle version currently being used.

Before restoring important courses into a live school site, it is best to test the restore on a staging site. This helps identify missing plugins, broken formats, and compatibility issues before teachers depend on the copied course.

Moodle Version and Cross-Site Restore Problems

Course restore can become more complicated when moving courses between different Moodle sites or different Moodle versions.

In general, restoring a course from an older Moodle version into a newer Moodle version is usually more practical than restoring a backup from a newer Moodle version into an older site. Problems can occur when the destination site does not support the same backup structure, activity types, course settings, or plugin versions.

Cross-site restores can also create conflicts with:

• Users and role assignments
• Groups and groupings
• Course categories
• Course formats
• Authentication settings
• Gradebook and completion settings

For example, a backup that includes users may behave differently when restored into a site that already has similar accounts or different role structures.

Schools may also run into issues when restoring courses between a production site, a staging site, and a department-specific Moodle site. Even when the Moodle versions are close, differences in plugin setup, file storage, permissions, and default settings can affect the result.

This is why schools should not treat course restore as a simple file upload in every situation. A course backup contains more than pages and files. It can also contain activity settings, gradebook structures, question banks, role information, completion settings, groups, and user-related data depending on the backup options selected.

For major course moves, schools should document the source Moodle version, destination Moodle version, required plugins, backup settings, and whether user data is included. A test restore should be completed before relying on the restored course for teaching.

Permissions and User Data Can Make the Process More Complicated

Sometimes Moodle course copy, backup, or restore does not work because the user performing the action does not have the correct permissions.

A teacher may be able to edit a course but not back it up. A department manager may be able to access a course category but not restore courses into it. A non-editing teacher may be able to view course content but not duplicate or import activities. These permission differences can make the process confusing for school staff.

Permissions become even more important when user data is involved. Moodle backups can include course content only, or they can include user data such as:

• Enrolled users
• Role assignments
• Submissions
• Grades
• Completion records
• Comments and logs
• Groups and groupings

For new academic terms, schools usually do not need to copy old student submissions, grade history, or completion records into the new course. Including user data can make the backup larger and can increase the chance of conflicts during restore.

A cleaner approach is often to copy the course structure and learning content without old student data. This helps teachers start the new term with the materials they need, while keeping past student records in the archived course.

Administrators should review role permissions carefully and decide who should be allowed to back up, restore, import, or copy courses. Schools should also define when user data should be included and when it should be excluded.

Best Practices for Schools Before Copying or Restoring Courses

Many Moodle course copy and restore problems can be prevented with a better preparation process.

Schools should maintain clean master course templates instead of repeatedly copying live courses from year to year. A master template can include the correct sections, activities, gradebook structure, completion settings, and standard resources without unnecessary student data or old course clutter.

Before copying a course into a new term, teachers or administrators should remove unused activities, old files, outdated links, hidden sections, duplicate labels, unnecessary blocks, and abandoned question categories. This keeps the course lighter and easier to copy.

Automated backups should also be reviewed regularly. Schools should schedule automated backups during low traffic hours, monitor backup reports, and make sure old backup files are not consuming too much storage.

It is also important to understand the difference between course backups and full-site backups. Course backups are useful for restoring individual courses, but they are not a complete disaster recovery strategy. A proper Moodle backup plan should also include the Moodle database, Moodledata, and Moodle codebase.

For larger schools, a staging site can be very helpful. Administrators can test course restores, plugin upgrades, large course copies, and backup settings before making changes on the live site. This reduces the risk of unexpected problems during term setup.

When Course Copy Problems Point to a Bigger Moodle Issue

When Moodle course copy, backup, or restore fails, the visible error is often only the symptom. The real cause may involve cron, hosting limits, plugin compatibility, database performance, file storage, permissions, or a recent Moodle upgrade.

Moodle expert developers can review the full environment instead of only looking at the course page. They can check server settings, task queues, logs, plugin dependencies, backup configuration, and course structure to identify the actual cause of the issue.

For schools, this can prevent repeated term-start problems. Expert support can help create reliable course templates, clean up old courses, optimize server settings, configure automated backups, test restore processes, and build a safer workflow for copying courses each year.

This helps teachers prepare courses more easily and gives administrators more confidence that Moodle backups and restores will work when needed.

Frequently Asked Questions (FAQs)