Since we were going to let it create 50k of MBZs and then pick out the ones we want to keep as an archive before deleting their course equivalent, it would really be better the other way - your way - send a list of courses we want to delete to be backed up and then not worry about the sorting process afterwards. But we don't have access to the command line, though the people that do have seen this thread and are watching. Plenty of space: we cloned live exactly and then doubled the disk space to allow for one run of MBZ files.Īs I imply, this doesn't need to be scheduled and automated: it is, at the moment, meant to be a one off, or perhaps annual, housekeeping process prior to deleting our first eight years' worth of courses! And the CLI mechanism does sound like a better option. and will run until complete - allows you to log out of the ssh session so you can sleep! which means it puts processing in the background of your shell session. There is also a way to run that script with 'nohang up'. So if you have CLI access be glad to share how to create a looping bash shell script that would backup every course from a cids.txt file (course ID numbers) and point those backups to a designated directory (which has to be manually created in advance of running script).Įven share the query of the DB from the command line to create the cids.txt file. I've had to resort to using that CLI script due to a course whose size was 130G plus and that would 'upset' auto backups every time and no way to exclude it. That script takes course default backup setting - settings like keep users or not. in admin/cli/ there is a backup.php script which allows you to backup a course by course ID *and* point the backup to a designated directory. If you have command line access, one can do their own thing with backups. How much free space does your server have?ĭo you have command line access to the server via ssh? SO I set it again, this time to 12.10 in the backup schedule and 11.15 in the scheduled task, but of course now it appears to have marked everything in the backup logs as only to be processed next Monday I can't seem to get it to clear that out so I can try again. I did kind of wonder if there was perhaps a time zone issue. It appears to have gone through the entire site and marked each course to be "next backup" at 10.50 *next* Monday. I have already culled about 10k courses that literally had no content and enrolments to reduce the overall number.īut now I've got to the point of setting up the automated course backup schedule and run into an issue.įirst time, I noticed the scheduled task was set to run at 50 minutes past each hour, so, it being 10.30 I set up the automated course backup schedule to run on Monday at 10.50, enabled it and waited. So we have cloned (completely, including files) the live system so we can start which is likely to be a big process of backing up about 50,000 courses. And we've agreed a timetable to run automated course backups to produce an MBZ file for every course in the system, before deciding which we want to keep as backup files and allow to be deleted on the Moodle site itself. My site is just starting, after many years of using Moodle, to want to archive old courses.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |