by Gerry F.
So do I only need to truncate the one table, mdl_backup_courses? That seems to be the one telling automated backups to keep skipping the same courses. It's 150+ courses that are being skipped so prefer something bigger than an exacto-knife ![wink]( "wink")
I guess I have an egg and chicken question. Is there a downside to truncating the mdl_backup_courses table? I would assume without anything in there, Moodle would think none of the courses were backed up and then backup all courses during the automated backup. OR, are courses added to that table when they are created with a laststatus code letting Moodle know they have never been backuped before? I guess that is why I wanted confirmation before wielding the axe.
FYI, I have the automated course backups going to seperate drive and not within moodledata.
I see you are enjoying retirement, if i read one of your older posts correctly. Thanks for hanging around here and continuing to help!
I guess I have an egg and chicken question. Is there a downside to truncating the mdl_backup_courses table? I would assume without anything in there, Moodle would think none of the courses were backed up and then backup all courses during the automated backup. OR, are courses added to that table when they are created with a laststatus code letting Moodle know they have never been backuped before? I guess that is why I wanted confirmation before wielding the axe.
FYI, I have the automated course backups going to seperate drive and not within moodledata.
I see you are enjoying retirement, if i read one of your older posts correctly. Thanks for hanging around here and continuing to help!