Sorry for late reply ... been busy! :|
| nextstarttime | courses |
+---------------------+---------+
| 2018-10-09 01:30:00 | 374 |
| 2018-10-17 01:30:00 | 1542 |
| 2018-10-29 01:30:00 | 119 |
Tis he year 2019. so nextstarttime above will never start, me thinks.
What happens when I would update all the rows and nextstarttime with the timestamp of tonight (2019-02-28 01:30:00)
A lot of courses = a lot of processing!!!! Maybe too much!!! How about trying to space that out
by a day for X number and by 2 days another set? Are all those courses still visible and enrolable?
What happens when I would truncate the table mdl_backup_courses?
Last time I messed with this, turncated the data in 3 tables. It was like autobackups had never been run before.
Massive ... and took a very long time.
Think I warned users on Friday @ 5:00 PM and told them what we were doing ... and to expect the site to be slow. At times, it was slow. It finally finished one round by Sunday. And I checked status all weekend long. :\
Got nervous about that so went to bash shell scripts where I could felt like I had greater control ... notice that's 'felt like' ... yes, new courses would not automagcially be added, but entity didn't launch any new courses with students participating very often - @ semester etc. to be expected.
'spirit of sharing', Ken