Moodle

Backup Failure for Course with Large File Sizes or Large Number of Students

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: 1.7
  • Fix Version/s: None
  • Component/s: Backup
  • Labels:
    None
  • Environment:
    Operating system Linux
    Kernel version 2.6.17.11-grsechg
    Machine Type i686
    Apache version 1.3.34 (Unix)
    PHP version 4.4.4
    MySQL version 4.1.21-standard
  • Affected Branches:
    MOODLE_17_STABLE

Description

When performing backups on courses with large sized files or a large number of users (700+), backup is timing out and not completing. Php max_execution_time has been adjusted to 150 with no improvement. Shared server host hesitant to go much higher. For access to example course write rich@rlsei.com.

Issue Links

Activity

Hide
Eloy Lafuente (stronk7) added a comment -

Hi Rich,

did you fixed this with your hosting company? Backup and restore are, by definition, BIG scripts and server needs strong resources while the size of the info to backup grows. Apart from continue minor improvements performed to code, I really think we cannot do too much against hard hosting limits.

Show
Eloy Lafuente (stronk7) added a comment - Hi Rich, did you fixed this with your hosting company? Backup and restore are, by definition, BIG scripts and server needs strong resources while the size of the info to backup grows. Apart from continue minor improvements performed to code, I really think we cannot do too much against hard hosting limits.
Hide
Wen Hao Chuang added a comment -

Hi Eloy we all know that backup and restore are BIG scripts but is there any efforts to make it even more efficient? Here at SFSU we also have some courses that have 1000+ students, and currently we could only use mysql dump to backup/restore these courses. It would be great if the course-level backup/restore could work for these large courses as well. Thanks!

Show
Wen Hao Chuang added a comment - Hi Eloy we all know that backup and restore are BIG scripts but is there any efforts to make it even more efficient? Here at SFSU we also have some courses that have 1000+ students, and currently we could only use mysql dump to backup/restore these courses. It would be great if the course-level backup/restore could work for these large courses as well. Thanks!
Hide
Dan Marsden added a comment -

I'm closing this bug as "incomplete" - there's not really enough information - where is the backup failing? - what error messages are showing? - is debugging turned on?

a range of performance related changes have been implemented in the latest 1.9, and some error checking has improved. so this persons issue may have been fixed.

MDL-14550 makes massive improvements for large sites with large numbers of users. (SFSU - this will probably improve things for you dramatically!)

Backup/restore is heavy, and I don't think it will ever run "smoothly" under a shared host environment, but there has been improvement, and there is still room for improvement - see the other bugs in the tracker for the backup module.

If you have more specific information about an inefficient part of the backup/restore that is not currently logged in the tracker, or an area where backup is failing with no debug output, feel free to create a new report! (but please check that a tracker issues doesn't already exist for your problem.)

thanks,

Dan

Show
Dan Marsden added a comment - I'm closing this bug as "incomplete" - there's not really enough information - where is the backup failing? - what error messages are showing? - is debugging turned on? a range of performance related changes have been implemented in the latest 1.9, and some error checking has improved. so this persons issue may have been fixed. MDL-14550 makes massive improvements for large sites with large numbers of users. (SFSU - this will probably improve things for you dramatically!) Backup/restore is heavy, and I don't think it will ever run "smoothly" under a shared host environment, but there has been improvement, and there is still room for improvement - see the other bugs in the tracker for the backup module. If you have more specific information about an inefficient part of the backup/restore that is not currently logged in the tracker, or an area where backup is failing with no debug output, feel free to create a new report! (but please check that a tracker issues doesn't already exist for your problem.) thanks, Dan

People

Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: