Course backup: Difference between revisions

From MoodleDocs
 
(83 intermediate revisions by 15 users not shown)
Line 1: Line 1:
{{Course admin}}
{{Backup}}
A course can be saved with some or all of its parts by using the course backup.  Typically, the site administrator will set a schedule of site wide backup for all courses.  A teacher with editing privileges can create a backup or download an existing backup for safe keeping, or for use on another Moodle site.   
A course can be saved with some or all of its parts by using the course backup.  Typically, the site administrator will set a schedule of [[Automated course backup|automated course backups]] for the whole site.  A teacher can create a backup or download an existing backup for safe keeping, or for use on another Moodle site.   


{{MediaPlayer | url = https://youtu.be/DnKA95x3DWI| desc = Course backup}}


==Creating a course backup==
[[Image:Course_backup.jpg|thumb|Creating a course backup - page 1]][[Image:Course_backup_s2.jpg|thumb|Creating a course backup - page 2]][[Image:Course_backup_s3.jpg|thumb|Creating a course backup - page 3]]
[[Image:Backupdirectory.png|200px|thumb|left|alt text]]
To create a course backup:
#Click Backup in the [[Course administration block]].
#Select your backup options (Page 1)
##Choose the activities and resources you want to include, the default is everything. 
###The Include All/None links at the top will check or uncheck all the boxes in a column.
###Use the individual boxes to select or unselect specific parts of the course for the backup.
##Select course options desired at the bottom (see Backup options below)
#Click the Continue button to start the backup process.
#On the next page (Page 2)
##You can edit the default backup filename at the top of this page (uses format:backckup-COURSESHORTNAME-DATE-TIME.zip).
##You will see the backup details, a list of files and user data that Moodle will include in the backup
#Click the Continue button at the bottom. Or if this does not look right, use cancel to exit the backup process or use your back browser arrow to return to the initial course backup page.
#On the next page (Page 3), the progress of the backup is displayed.
##You should see the message "Backup completed successfully" at the bottom of the page.
#Click the Continue button.
#You will then be taken to the backupdata directory.
##You may click on a filename to download any backup file to your computer.
## Later this area can be reached by the Course administration block by using the Restore link or looking for what is usually called the backupdata folder under the Files link.


==Backup options==
==Backing up a course==
* User data -consists of all student files, submissions, forum postings, glossary entries, etc.
 
* Metacourse - If you are backing up the content of a [[Metacourses|metacourse]], you may enable this option so that relations between the courses will be exported and the restore process will try to rebuild them in the destination server.
To backup a course
* Users - Whether you want to backup the content concerning all the registered students in your site, only course students or no students at all. By selecting "none", the backup process will not backup user data
 
* Logs - This backs up all course activity logs.
# Go into the course.
* User files - This backs up all student submissions for assignments and other file uploads.  
# From Course navigation > More > Course reuse, select 'Backup'.
* Course files - This backs up any file stored in the [[Files|files]] area for the course.
# Initial settings - Select activities, blocks, filters and other items as required then click the Next button. Users with appropriate permissions, such as administrators and managers, can choose whether to [[Backup of user data|include users]], anonymize user information, or include user role assignments, groups, groupings, user files, comments, user completion details, course logs and grade history in the backup.
# Schema settings  - Select/deselect specific items to include in backup, then click the Next button.
# If desired, select specific types of activity to be backed up by clicking the link 'Show type options'
# Confirmation and review - Check that everything is as required, using the Previous button if necessary, otherwise click the 'Perform backup' button
# Complete - Click the Continue button
 
{|
[[File:backupsettings42.png|thumb|Backup settings]]
|
|[[File:26backuprestore1.png|thumb|Back up screen with option to select all or none]]
|
|[[File:26backuprestore2.png|thumb|Back up screen with option to select activity types]]
|}
 
A backup file (with distinctive .mbz extension to avoid confusion with .zip files) is then saved in the course backup area. Backup file names are of the form ''backup-moodle2-course-coursename-date-hour.mbz'', ending in ''-nu.mbz'' when backed up with no users and ''-an.mbz''  with anonymized names.
 
Tip: If you are satisfied with the default settings and don't wish to go through all the backup screens, you can simply click 'Jump to final step' to perform the backup.
 
==Anonymizing user information==
 
Anonymize user information is a backup feature which "protects user identities" by making each user anonymous. If this box is checked in the backup initial settings, Moodle will substitute aliases for real names, substituting @doesntexist.com email addresses and so forth. For example  "Max Manager" might become  "anonfirstname4 anonlastname4".
 
==Asynchronous course backups==
 
Note: With large courses it is helpful to be able to continue working while a course backup is being made. To achieve this, you need to enable asynchronous backups in ''Site Administration / Courses / Backups / Asynchronous backup/restore''.
 
==Backup via CLI for administrators==
 
Site administrators can backup selected courses using a CLI script.
 
Options
--courseid=INTEGER (Course ID for backup.)
--courseshortname=STRING (Course shortname for backup.)
--destination=STRING (Path where to store backup file. If not set the backup will be stored within the course backup file area.)
-h, --help (Print out this help.)
 
Example
sudo -u www-data /usr/bin/php admin/cli/backup.php --courseid=2 --destination=/moodle/backup/
 
On Windows you will use cmd.exe to run the /admin/cli/backup.php script. If you have your Moodledata folder setup on a separate data server you can specify a UNC path to your backup folder on that data server. From the command line CD to the Moodle ''\admin\cli'' folder and run this command:
php backup.php --courseid=25 --destination=\\moodledata\backup
 
where '--courseid' is the id of the course that you want to backup.
 
The .mbz backup file for courseid=25 will be stored in the ''backup'' subfolder in the ''Moodledata'' ($CFG->dataroot) folder.
 


==Creative uses==
==Creative uses==
Line 40: Line 65:
*In earlier versions of Moodle, a way of rolling a course forward without past student activity
*In earlier versions of Moodle, a way of rolling a course forward without past student activity
*Creating a blank activity, save just that activity and then restore it to the course or another course one or more times.  
*Creating a blank activity, save just that activity and then restore it to the course or another course one or more times.  
:''Note:'' The Moodlesite may automatically make and delete backups. For example, it may backup each individual course daily, but not keep any of these backups longer than 5 days. Manual backups by the teacher are usually not effected by this process.
 
==General backup defaults==
 
Default settings for course backups can be set by a site administrator in 'General backup defaults' in the Site administration.
 
Selected settings may be locked, so that they cannot be changed when creating a course backup.
 
By selecting a time in the "Keep logs for.."  dropdown, it is possible to specify how long backup  logs information is kept before being deleted. As this information may be very large, it is recommended the length of time chosen be quite short.
 
==Course backup stops above 90%, not showing any errors==
This has been reported to be caused by:
* a [[Course_formats#Contributed_Course_Formats|non-standard course_format]]. Try replacing the course format.
* not enough server RAM. Adding more RAM to your server is usually the first [[Performance_recommendations|performance recommendation]].
 
==Course backup capabilities==
 
*[[Capabilities/moodle/backup:anonymise|Anonymise user data on backup]]
*[[Capabilities/moodle/backup:backupcourse|Backup courses]]
*[[Capabilities/moodle/backup:backupsection|Backup sections]]
*[[Capabilities/moodle/backup:backuptargetimport|Backup for import]]
*[[Capabilities/moodle/backup:configure|Configure backup options]]
*[[Capabilities/moodle/backup:downloadfile|Download files from backup areas]]
*[[Capabilities/moodle/backup:userinfo|Backup user data]]
 
==Error: Trying to restore user 'admin' from backup file will cause conflict ==
* Before proceeding, it would be advisable to have a second admin account ''just in case something goes wrong''.
* Check that the admin accounts on each server have '''different''' unique usernames and email addresses and then try again to backup up the course with user data and restore it.
** If you can not make a new backup and you must use an existing 'conflicting' backup file, you will have to change the new site's main admin account with extreme care to remember the new main admin's password and email.
* Note that the admin account from the imported file may loose the password and become unusable;
* You are advised to update/reset the 'imported' main 'admin's account's password before logging out, as this will most likely be the main 'admin' account for the site, and you would get into serious problems if this account stops working.
* If something goes terribly wrong, you can use the second admin account to fix the main admin account.  


==See also==
==See also==


*[[Restore]]
*[[Course restore]]
*[[Backup settings]] - for administrators
*[[Backup of user data]]
*[[Backup and restore FAQ]]
*[[Activity backup]]
*[[Roll courses forward]]
* Administrators can use [http://moosh-online.com/commands/#course-restore MOOSH] to bulk backup and restore courses from CLI
*[[Front Page]] trick to backup Front page in earlier version of Moodle
*[http://www.youtube.com/watch?v=ZrdM_KOr530 Creating course backups video]
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=59581 Location of Backup Files] forum discussion


[[Category:Backup]]
[[Category:Course]]


[[de:Kurssicherung]]
[[es:Respaldo del curso]]
[[eu:Ikastaroaren_Segurtasun-kopia]]
[[fr:Sauvegarde de cours]]
[[fr:Sauvegarde de cours]]
[[es:Copia de Seguridad del Curso]]
[[ca:backup/backup]]
[[ja:コースバックアップ]]
[[ja:コースバックアップ]]
[[de:Kurssicherung]]

Latest revision as of 08:39, 23 August 2023

A course can be saved with some or all of its parts by using the course backup. Typically, the site administrator will set a schedule of automated course backups for the whole site. A teacher can create a backup or download an existing backup for safe keeping, or for use on another Moodle site.

Course backup


Backing up a course

To backup a course

  1. Go into the course.
  2. From Course navigation > More > Course reuse, select 'Backup'.
  3. Initial settings - Select activities, blocks, filters and other items as required then click the Next button. Users with appropriate permissions, such as administrators and managers, can choose whether to include users, anonymize user information, or include user role assignments, groups, groupings, user files, comments, user completion details, course logs and grade history in the backup.
  4. Schema settings - Select/deselect specific items to include in backup, then click the Next button.
  5. If desired, select specific types of activity to be backed up by clicking the link 'Show type options'
  6. Confirmation and review - Check that everything is as required, using the Previous button if necessary, otherwise click the 'Perform backup' button
  7. Complete - Click the Continue button
Backup settings
Back up screen with option to select all or none
Back up screen with option to select activity types

A backup file (with distinctive .mbz extension to avoid confusion with .zip files) is then saved in the course backup area. Backup file names are of the form backup-moodle2-course-coursename-date-hour.mbz, ending in -nu.mbz when backed up with no users and -an.mbz with anonymized names.

Tip: If you are satisfied with the default settings and don't wish to go through all the backup screens, you can simply click 'Jump to final step' to perform the backup.

Anonymizing user information

Anonymize user information is a backup feature which "protects user identities" by making each user anonymous. If this box is checked in the backup initial settings, Moodle will substitute aliases for real names, substituting @doesntexist.com email addresses and so forth. For example "Max Manager" might become "anonfirstname4 anonlastname4".

Asynchronous course backups

Note: With large courses it is helpful to be able to continue working while a course backup is being made. To achieve this, you need to enable asynchronous backups in Site Administration / Courses / Backups / Asynchronous backup/restore.

Backup via CLI for administrators

Site administrators can backup selected courses using a CLI script.

Options

--courseid=INTEGER (Course ID for backup.)
--courseshortname=STRING (Course shortname for backup.)
--destination=STRING (Path where to store backup file. If not set the backup will be stored within the course backup file area.)
-h, --help (Print out this help.)

Example

sudo -u www-data /usr/bin/php admin/cli/backup.php --courseid=2 --destination=/moodle/backup/

On Windows you will use cmd.exe to run the /admin/cli/backup.php script. If you have your Moodledata folder setup on a separate data server you can specify a UNC path to your backup folder on that data server. From the command line CD to the Moodle \admin\cli folder and run this command:

php backup.php --courseid=25 --destination=\\moodledata\backup

where '--courseid' is the id of the course that you want to backup.

The .mbz backup file for courseid=25 will be stored in the backup subfolder in the Moodledata ($CFG->dataroot) folder.


Creative uses

The backup and restore processes can offer the teacher and administrators many creative solutions.

  • Duplicating courses or specific activities in one course to another course (similar to Import)
  • Updating a production Moodle site course, with material from a localhost site course
  • Transferring a course to a new Moodle site.
  • In earlier versions of Moodle, a way of rolling a course forward without past student activity
  • Creating a blank activity, save just that activity and then restore it to the course or another course one or more times.

General backup defaults

Default settings for course backups can be set by a site administrator in 'General backup defaults' in the Site administration.

Selected settings may be locked, so that they cannot be changed when creating a course backup.

By selecting a time in the "Keep logs for.." dropdown, it is possible to specify how long backup logs information is kept before being deleted. As this information may be very large, it is recommended the length of time chosen be quite short.

Course backup stops above 90%, not showing any errors

This has been reported to be caused by:

Course backup capabilities

Error: Trying to restore user 'admin' from backup file will cause conflict

  • Before proceeding, it would be advisable to have a second admin account just in case something goes wrong.
  • Check that the admin accounts on each server have different unique usernames and email addresses and then try again to backup up the course with user data and restore it.
    • If you can not make a new backup and you must use an existing 'conflicting' backup file, you will have to change the new site's main admin account with extreme care to remember the new main admin's password and email.
  • Note that the admin account from the imported file may loose the password and become unusable;
  • You are advised to update/reset the 'imported' main 'admin's account's password before logging out, as this will most likely be the main 'admin' account for the site, and you would get into serious problems if this account stops working.
  • If something goes terribly wrong, you can use the second admin account to fix the main admin account.

See also