Error Checking Backup File. Moodle.xml
Also, if possible, it's highly recommended to solve those problems in the original course too from Moodle itself. I suspect that might be a task too far, if that is your issue. Retrieved from "https://docs.moodle.org/24/en/index.php?title=Backup_and_restore_FAQ&oldid=104846" Categories: BackupFAQ 2.4 docs 3.1 docs3.0 docs2.9 docs2.7 docs Views ArticlePage CommentsView sourceHistory Personal tools Log in Navigation Main page Table of contents Recent changes Docs overview Tools This part of the backup (or restore) procedure tries to delete old info, used in previous executions, performing the following tasks: Delete old records from "backup_ids" table: Check the table exists, http://megavoid.net/error-checking/error-checking-log-file.html
Moodle will create the course file folders as long as the unclean moodle.xml file. These are "controlled" errors and the scheduled backup continues with the next course. See Site backup. I Still get an XML error. https://docs.moodle.org/24/en/Backup_and_restore_FAQ
Error Checking Backup File. Moodle.xml
In such cases you may want to try the following: Download the Atlassian XML Cleaner Utility from the JIRA Atlassian site. Rename the unclean moodle.xml file to moodle-unclean.xml. Main page ► Managing a Moodle site ► Backup ► Backup and restore FAQ Backup Site backup Course backup Course restore Automated course backup Year-end procedures IMS CC import and export
Post to Cancel HOME | SEARCH | REGISTER RSS | MY ACCOUNT | EMBED RSS | SUPER RSS | Contact Us | Backup and restore http://moodle.org/rss/file.php/127/1b51bf7f3cab9689af042af1ff4a07f0/mod_forum/128/rss.xml (c) 2016 Moodle - Open-source Obviously I have changed the names in that error message, but it is not just previous students (who may not have user account here anymore)affected. There is a moodle_backup.xml file, making me think that someone knew what s/he was doing when s/he created the course in Moodle. Another thought: might the course have been created I added a few lines to restorelib.php to check for the next level down when the top didn't exist/work (patch attached in prior comment).
These checks and behaviour were introduced in Moodle 1.9.x and continue being valid under 2.0. By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). https://tracker.moodle.org/browse/MDL-24150 Me da un error:Error checking backupfile.
moodle.xml not found at root level of zip file. The backup file can actually be opened with any zip/unzip program you can download. If you don't have access to your Moodle server's command prompt, using the Moodle zip feature, zip the moodle-unclean.xml file only, download the zip file locally and unzip it. Moodle™ is a registered trademark.
Backup files are copied to "XXX/backupdata" under your dataroot directory (where XXX is the id of the course being backed up). They can be found, and deleted easily, in the directory tree of the backup. Error Checking Backup File. Moodle.xml Leaving them out saves huge amounts of disk space and makes the backup procedure much faster. It's caused when the XML parser detects something incorrect in the backup file that prevent correct operation.
A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). have a peek at these guys Incorrect settings also lead to this error message (see the Using Moodle forum discussion moodle.xml not found in root... It is also giving the error message about staff members who do still have active accounts in Moodle. To obtain precise information about what's happening, you can enable debug messages in Administration > Server > Debugging (select the maximum level - DEVELOPER) and/or check the web server error logs.
You can then rezip the edited file, rename it to an mbz and, if you have edited it right, it should restore. Show Chris Warren added a comment - 09/Sep/10 11:37 PM doh - on further test, the course copy still doesn't work (with the oh-so-informative "An error occurred" message). If you are restoring from a zip file backup make sure the moodle.xml file is at the root level. check over here Once uploaded, unzip it using the Moodle unzip feature.
Like this:Like Loading... Scales are only backed up if they are used by at least one activity. a forum) was minimal.
If you go there with an FTP program you can see what is there and clean up.
Incorrect settings also lead to this error message. Because of the way files are stored in Moodle 2.x, there is no need to include the files in the backup if you are planning to restore them to the same There are two possible methods to make the xxxx users match (and avoid the conflict): a) Modify the backup archive users.xml file and make the email or firstaccess fields match the Now, I wait If my cronjob works...
moodle.xml not found at root level of zip file) dice que en el archivo .zip que genera la copia, debería haber un fichero .xml en el directorio raíz, es decir que Attempting to restore a course to an older version of Moodle than the one the course was backed up on can result in the restore process failing to complete. Instead, please try the following: Make a clean install of Moodle 1.5.x (the latest version available) Restore all your courses there (they should work if they were working originally) Upgrade your this content Why does restore stop, rather than completing?
Edit the moodle.xml file with some UTF8-compatible editor and delete such characters. By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), See Course restore. To ensure this: Unzip the backup file of the course (example: mycourse.zip) Once the file is unzipped, open the folder (example: mycourse).
It's common for the user in question to be the "admin" user (which exists in practically all Moodle installations). Repeat this for all the files required, using the correct contenthash value of course. Up-to-date documentation for the latest stable version of Moodle may be available here: Backup and restore FAQ. Restore the course.
Attempting to restore a course to an older version of Moodle than the one the course was backed up on can result in the restore process failing to complete. Site policy | Privacy | Contact Linked ApplicationsLoading… DashboardsProjectsIssuesCaptureGetting startedcute element Home Documentation Downloads Demo Tracker Development Translation Moodle.net Search All content on this web site is made available under the Delete old files from "moodledata/temp/backup": Delete the dir completely and try again. In Reports/backup there is now a log file - yippie, but it says, that every course is skipped. The complete file is in the attachment.
The recovery time to have a site running again takes longer than a site backup. To obtain precise information about what's happening, you can enable debug messages in Administration > Server > Debugging (select the maximum level - DEVELOPER) and/or check the web server error logs.