We appear to have over 2,500 .mbz backup files in our recycle bin despite not having automated backups on, so I have no idea how we accumulated so many. For context, we run about 800 courses a semester, the instance was created fresh this summer, we only have a little over a thousand courses total. So somehow all (or most) of our courses are being backed up a few times a week into the bin. It's a massive burden on our file storage system, nor do we have any idea how to even access and use all these backups stored in the recycle bin even if we wanted to, so I'd love to prevent this from happening.
Here's the ad hoc report I used to discover this:
SELECT id, filename,
CONCAT(CEILING(filesize / 1048576.0), 'mb') as size,
component, filearea,
FROM_UNIXTIME(timecreated, '%Y %D %M %h:%i:%s') as time_created,
FROM_UNIXTIME(timemodified, '%Y %D %M %h:%i:%s') as time_updated
FROM {files} f
WHERE filename LIKE '%.mbz'
AND (component = "tool_recyclebin"
OR filearea = "recyclebin_course")
ORDER BY filesize DESC
And here are some sample result rows:
idfilenamesizecomponentfileareatime createdtime updated1backup.mbz2597mbtool_recyclebinrecyclebin_course2020 2nd September 03:20:592020 2nd September 03:25:172backup.mbz2597mbtool_recyclebinrecyclebin_course2020 2nd September 03:25:522020 2nd September 03:28:053backup.mbz863mbtool_recyclebinrecyclebin_course2020 1st September 05:20:512020 1st September 05:21:134backup.mbz862mbtool_recyclebinrecyclebin_course2020 1st September 05:35:092020 1st September 05:35:33