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

Moodle relies on cron and background tasks to process course copies, backups, restores, and automated backups. If these tasks stop processing, jobs can remain queued even when the rest of the site appears normal.

Common signs

• Course copies stay In progress
• Backup jobs never finish
• Automated backups stop running
• Restore processes remain incomplete
• Ad hoc tasks build up in the queue

What to check

• Is Moodle cron running on schedule?
• Are scheduled tasks overdue?
• Are ad hoc tasks stuck?
• Are many backup or restore jobs running at the same time?

For a stuck course copy, cron and the task queue should be one of the first checks.

Course Files, Media, and Server Limits Are Too Large

Plugin, Theme, or Course Format Compatibility Issues

A Moodle course can depend on plugins and formats that do not exist—or do not work the same way—on the destination site.

Problems commonly occur when

• The destination is missing a required plugin
• A plugin is disabled or outdated
• The course uses an unsupported activity or question type
• The source and destination use different course formats
• A theme-specific block or layout behaves differently
• The course was created before a major Moodle upgrade

What to check before restore

• Compare installed plugins on both sites
• Confirm plugin versions support the destination Moodle version
• Check custom question types and course formats
• Review theme-specific blocks or layouts
• Test the restore on staging first

A restore can technically complete while still leaving missing or broken activities, so visual and functional testing is important.

Moodle Version and Cross-Site Restore Problems

Moving a course between Moodle sites becomes more complex when the versions, plugins, or configurations differ.

Check these differences first

• Moodle version
• Installed plugins
• Course formats
• User and role structures
• Groups and groupings
• Gradebook settings
• Completion settings
• Authentication configuration

Pay special attention to user data

Backups containing users can create additional conflicts with:

• Existing accounts
• Different role assignments
• Previous enrolments
• Groups
• Grades
• Completion records

For an important migration, document the source version, destination version, required plugins, backup settings, and whether user data is included, then perform a test restore before production use.

Permissions and User Data Can Make the Process More Complicated

Not every Moodle user who can edit a course is allowed to back it up, restore it, import content, or create courses elsewhere.

Check user permissions for

• Course backup
• Course restore
• Course import
• Course copy
• Course creation in the destination category

Backups can also contain

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

For a new term

In most cases, copy:

• Course structure
• Activities
• Resources
• Question banks
• Gradebook structure
• Completion settings

Avoid copying old learner data unless it is specifically required.

Keeping previous student submissions, grades, and completion records in the archived course usually creates a cleaner new-term course and a smaller backup.

Best Practices for Schools Before Copying or Restoring Courses

Most copy and restore problems are easier to prevent than troubleshoot later.

Use clean master templates

Maintain a reusable course template containing:

• Standard sections
• Required activities
• Gradebook structure
• Completion settings
• Current resources

Avoid repeatedly copying an old live course year after year.

Clean the course before copying

Remove:

• Old files
• Unused activities
• Outdated links
• Hidden content no longer needed
• Duplicate resources
• Old backup files
• Abandoned question-bank content

Manage automated backups

• Schedule backups during lower-traffic periods
• Review backup reports
• Limit retention
• Monitor backup storage
• Investigate failed or oversized backups

Maintain full-site backups too

Course backups are not a complete disaster-recovery plan.

A complete Moodle backup strategy should also protect:

• Moodle database
• Moodledata
• Moodle code
• Plugins and themes
• Configuration files

Use staging for important changes

Test:

• Large course restores
• Cross-version restores
• Plugin upgrades
• Backup configuration
• Course copies

before making the same change on production.

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)