 Moodle gives you a few ways to back up your online courses. Firstly, through the eyes of a site administrator, you log in via the front page. You go to the site administration block and the courses menu and then backups. These site-wide backups can be configured to run automatically on a nightly or a weekly basis. However you like, you can choose to include any or all modules and users and logs, files and grades and so forth. You choose how many versions you want to retain. If you only keep one version each time you back up, naturally the older version will be overridden. You need to schedule the backups. In fact, check the box to set them as active. If they're not automated, site-wide course backups aren't activated by default. Then choose the day or days you wish to run the automated backups and the time. By default these get written into the backup data directory located in each course. I'll show you where that is. The automated backups will only run for active courses. Hidden courses aren't included in backups because it's presumed nothing has changed since the course was made inactive. If we go into an active course and we presume that the Cron job has been configured and is executing, all these automated site-wide backups can also run. If we go into the files area for any given active course, the backup data directory, as we said, will have the backup situated in its date and time stamp there. You can see it's a zip file. We could restore this at any point in time. It's a fairly sensible thing that educators want to do. At the end of a term or semester or an academic or calendar year, you want to clone a course and perhaps strip away the user. You can run a similar course next year with the teacher contribution still intact, but you want to strip away your existing users. This backup was already done. We get an option here. We can restore to a current course or an existing course adding or deleting data first. In this case, let's say we want to restore this backup to a new course. It's going to be a clone or a copy of the existing one. Without user data. However, we will include all the activities and the resources. Strip away the users and we'll keep everything else there. We would continue that. Let's restore this backup. We're essentially cloning or copying the existing course, but stripping away the users and their data for the next cohort. That restore has been done and that's a clone of the original course. Another way to go, typically educators might want to come in periodically from time to time and not rely on the automated backups that may or may not be occurring system-wide. As an editing teacher, run a backup of a course at any point in time. You come in to the course administration block and you click the backup function. Like so. Again, we can select all or none of the activities, the resources and the user data and continue to click through this wizard continue again. And we have successfully completed a manual backup. Continue. All right. So the backup file resides in the backup data directory of the given course. What we can then can do is download and save this file locally. So that means off site or offline on a disk away from the Moodle server. It's a clever thing to do. I guess for data security and disaster recovery purposes, it's never a bad idea to have a backup. So we've done that. You could then, in fact, if you wanted to free up a little bit of your storage space with your host or on your server, you would then be able to potentially delete the backup that you've got stored online. Like so.