So if you clicked the button that says "manage backup files", what happens? There should be a page refresh and in the box it should show those files listed in the table as icons file their .mbz filenames. To remove them, right click or control click on single file and there should be a button atop the next popup window to delete the file. After deleting all of them, remember to save ... that last action updates the tables. Remember, you are looking at meta-data read from database tables ... not the real files themselves. The files themselves should be moved to trashdir on the next cron job run and there (in trashdir) they remain until 4 days passes, at which time, via another cron job, the files are finally removed from the drive.
"course restore space" IF the backups are going to the default area for backups, which in the config for automated backups is Automated backup storage
backup | backup_auto_storage and is set to Default: Course backup filearea. Translated that means in moodledata/filedir/ That's why they show in the area of your screen shot.
There is also another setting for
which is a directory you manually create and make readable/writable by the apache user.
There are other settings which, if the tables were truncated, would from this time forward come into play.
Keep number. Skip courses not modified. Skip hidden courses.
So it's really a combination of factors that determines what one sees. Truncating all tables removes any data Moodle was keeping on courses, but doesn't necessarily change the behavior of the options chosen for automated backups.
If I re-call correctly, with the two sites I was having trouble with, I had to truncate the new data created those tables. then fiddled with the settings for automated backups again to get desired results.
I ran the automated backups from the command line. After running, needed to get into any course and click restore to see the backup files IF they were saved in an area I can see via Moodle UI. Moodle doesn't provide an admin tool/view of all course backups. Would also check, via command line, that alternate directory I manually created for the presence of the backups. I saved those to a directory like: /home/m29backups which is writable by apache.
'spirit of sharing', Ken
'spirit of sharing', Ken