https://docs.moodle.org/33/en/Backup_and_restore_FAQ says that unfinished backups are skipped next time
- Unfinished - this happens when the backup procedure dies without knowing why. When the cron is next executed it detects that the last execution went wrong, and continues skipping the problematic course. A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), or if there is some exact point were all the courses are breaking.
while https://docs.moodle.org/33/en/Automated_course_backup says that unfinished backups are completed next time
- Unfinished - The backup was not finished. This might have happened because the job to execute backups ran out of time or resources (e.g., the cron running the backups ran out of time before finishing all the courses waiting). The unfinished jobs should be completed when the next scheduled backups are repeated.
Which of the statements is correct?
In my 3.3. system it seems that unfinished backups are not completed - which leads do many unfinished Backups now. If unfninished backups are skipped, how can I ever get a backup again. I could not find a way to reset the backup status.