by Marius S.
Hello Alain, we have this option enabled in automated backup settings, and 'filescleanupperiod' is set to 3 weeks.
However as I mentioned as we are doing automated backup to moodledata + specific directory (mbz files), so checking specific directory I can see that every week is similar number of backups made and it's about 240-280GB. So I assume that backups in Moodledata uses more or less same space. So each week ~240GB of new backups are stored in moodledata and ~240GB should be deleted.
We have 600GB free space if moodledata/trashdir and moodledata/temp/backup is empty.
And this weekend I checked moodledata/trashir after automated backups finished so we had ~540GB in trashdir and only 60GB free space.
Also now we run our cli cron every 5 minutes. So I don't understand why moodledata/trashdir are getting so big when we start automated backups on weekends.
Even if oldest backups are moved to trashdir and deleted only after 24 hours it should be plenty of free space left as new backups size are the same every week ~240GB..
Marius.
However as I mentioned as we are doing automated backup to moodledata + specific directory (mbz files), so checking specific directory I can see that every week is similar number of backups made and it's about 240-280GB. So I assume that backups in Moodledata uses more or less same space. So each week ~240GB of new backups are stored in moodledata and ~240GB should be deleted.
We have 600GB free space if moodledata/trashdir and moodledata/temp/backup is empty.
And this weekend I checked moodledata/trashir after automated backups finished so we had ~540GB in trashdir and only 60GB free space.
Also now we run our cli cron every 5 minutes. So I don't understand why moodledata/trashdir are getting so big when we start automated backups on weekends.
Even if oldest backups are moved to trashdir and deleted only after 24 hours it should be plenty of free space left as new backups size are the same every week ~240GB..
Marius.