Hi Ken,
Thanks for your response! Overnight, Moodle seems to have cleared the running status itself - however, the task is now failing when trying to pick up where it left off - and I *think* I have a theory... maybe?
So yesterday, when the task was running normally and interrupted (we think it was killed gracefully by accident as the last line in the cron log was "Terminated: 15". However, that did not clear the running status. After spending some time trying to research this, my understanding is that there is a status value set somewhere in the Moodle db, potentially for the individual course(s) that is(are) currently being backed up that results in the "running" status response. I'm not sure of this as of this morning since the status did clear overnight and now the task is failing when it attempts to backup the first course where I'm guessing it left off:
Skipping COMM-001-010-FL18-Media and Society (Not scheduled for backup until Sat, 29 Feb 2020 03:00:00 -0500) Backing up COMM-001-011-FL18-Media and Society... ... used 10324 dbqueries ... used 5.2991099357605 seconds Scheduled task failed: Automated backups (core\task\automated_backup_task),error/setting_already_added
Skipped courses appear first (there are a bunch) and then on the first actual course backup attempt I receive the above error. I'm wondering if there is a status value in the db somewhere or a temp file I should delete to resolve this error. Unfortunately, we have just over 18,000 courses in the system, so deleting all temp files and forcing a new backup of all courses is truly a very last resort (takes about 72 hours to complete a backup of all courses).
Thanks for the plugin recommendation, I will check that out. Most of my work is done from the command line because of how large our site is - I can't even load the course backup log from the web GUI because of how many courses we have.
Thanks so much again for your response.