by Indra Abdurojak.
>> Hi Ken, I'm surprised your guess is exactly what I'm going to do. I have discussed with the team and will make a fresh install moodle for next academic year, while existing moodle will be records retention for next 5 years. So I don't need to do backup-restore all courses.
>> Thanks for the sharing and advising, I really appreciate that.
Success always Ken.
Indra from indonesia.
"I think you are taking the wrong approach to this archive server instance. Why aren't you cloning production server to an archive server (site migration really) every year?
Then once the archive server is up and can be accessed, in production server, reset all courses (moosh has a command for that) removing users with role ID 5 (students) from each course. That command could be put into a looping bash shell script that resets only the course ID's in a text document that contains nothing but the course ID's.
I take it that this archive server is for the purpose of records retention ... correct?
How long is that? 5 years? Then you have to have enough space on a server to host 5 archive instances. tld below means top level domain ... like 'mygreat.edu'"
>> Hi Ken, I'm surprised your guess is exactly what I'm going to do. I have discussed with the team and will make a fresh install moodle for next academic year, while existing moodle will be records retention for next 5 years. So I don't need to do backup-restore all courses.
>> Thanks for the sharing and advising, I really appreciate that.
Success always Ken.
Indra from indonesia.