Talk:Automated course backup

SQL dump

I wonder if administrators should be recommended to use mysqlhotcopy rather than mysqldump. Although mysqldump outputs a handy SQL file, it does not lock tables before being called, so there is the potential for data inconsistency on large/busy sites. mysqlhotcopy locks tables before making copies of the table files themselves. These can be tarred & gzipped for copy to another disk/server:

#!/bin/sh
#
# clear moodle backup directory
rm -R /var/backups/databases/moodle/*
#
# hotcopy moodle tables
mysqlhotcopy --addtodest -u <username> -p <password> moodle /var/backups/databases
#
# tar & gzip them
tar -czf <path_to_homedir>/moodle-db-`date +%Y%m%d`.tar.gz /var/backups/databases/moodle

clarification of exclusion

I am referring to "Note: From 1.6 onwards, course backups automatically skip courses which are unavailable to students AND have not been changed in the last month." The capitalized "and" could imply that a) any course that is unavailable to students should still be backed up if it was changed; b) any changed course will be backed up only if it is not available to students. I suspect that the sentence should really read: "Note: From 1.6 onwards, course backups automatically skip courses which are unavailable to students and courses which have not been changed in the last month." (no need to capitalize the "and"). In other words, either of the conditions will exclude the course from backup.

Robert, thanks for your comments. You're right that either of the conditions will exclude the course from backup, and so I've reworded the note accordingly. --Helen Foster 08:08, 3 October 2008 (CDT)