by Jock Coats.
3.11.6
Plenty of space: we cloned live exactly and then doubled the disk space to allow for one run of MBZ files.
As 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. But we don't have access to the command line, though the people that do have seen this thread and are watching.
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.
I don't have direct access to the database, but we do get a nightly backup so I can run queries against that to generate the list based on whether or not they have active enrolments, been modified for a certain period and so on, and feed a process such as you are suggesting if our hosting partners would be willing to do that. Feels safer to me than setting up an "automated schedule" for something that we don't need either scheduled or automated!![smile]( "smile")
Our new partition was already added, mounted and tested as being writeable by the www-data user on a mount point below /moodle (though it would have been even cooler if doing it all from the command line to mount our cold storage drive direct if we knew we were only going to be backing up what we wanted backed up!)
Cheers,
Jock
As 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. But we don't have access to the command line, though the people that do have seen this thread and are watching.
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.
I don't have direct access to the database, but we do get a nightly backup so I can run queries against that to generate the list based on whether or not they have active enrolments, been modified for a certain period and so on, and feed a process such as you are suggesting if our hosting partners would be willing to do that. Feels safer to me than setting up an "automated schedule" for something that we don't need either scheduled or automated!
Our new partition was already added, mounted and tested as being writeable by the www-data user on a mount point below /moodle (though it would have been even cooler if doing it all from the command line to mount our cold storage drive direct if we knew we were only going to be backing up what we wanted backed up!)
Cheers,
Jock