Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-26057

serverbackups based on /moodle /moodledata + mysql dump

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Not a bug
    • Affects Version/s: 2.0.1
    • Fix Version/s: None
    • Component/s: Backup
    • Labels:
      None
    • Environment:
      LAMP, Moodle 2.0.1, Debian Lenny / Ubuntu 10.04 Server, backup2l, rsync
    • Database:
      MySQL
    • Affected Branches:
      MOODLE_20_STABLE

      Description

      When doing a server-side backup of a Moodle 2 installation (/moodle /moodledata + dump of mysql database), the size of the backup files do not correlate with user activity inside Moodle 2: Even if no new files are added to Moodle by the users, rsync-based backup solutions still find so many changed objects inside /moodledata that the size of the backup is growing by 2GB every night - even if one excludes directories like temp, trashdir and the like inside /moodledata from the backup!

      I can only speculate on the reason: Does Moodle 2 change filenames when running its own course-room-backup? Does it change mtime stamps when running its own course-room-backup?

        Attachments

          Activity

            People

            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: