by Francis Doydora.
Okay so disk usage
MoodleData - 620G incrementing around 4G per day
Backup - 256G incrementing around 2G per day
Trash Size - atm 3.4G gets cleared every hour via Moodle settings
Temp Size - 227M, temp/backup/* gets cleared hourly via manual cron
Total Used - 1.1T
Use% - 59%
Available - 753G
Okay so we're planning on migrating Backup(256G) to NFS as Automated backup is already in "Specified Directory" only mode. But this specified directory is still in the server, once we've changed the location to the NFS, that will be a deduction of 256G or more, which is good. No plans on migrating filedir to NFS as of yet.
256G in backups is only 1 day's worth, with the migration to NFS, we can ramp that up to 2 days or maybe 3. No worries on NFS storage size.
My worry is the server as its available disk space is dwindling.
Let's say there are no failed backups, hence I will no longer need to activate the manual cron that deletes /temp/backup/* every hour.
So automated backup's process looks like this (correct me if I'm wrong).
Auto Backup Starts > backup one course > store in temp/backup > compile > copy to NFS.
My concern is how long will the automated backup task leave the copy of the course in the temp/backup before it gets deleted? Is there a way to delete the temp/backup's copy in real time right after it has been copied to NFS?
MoodleData - 620G incrementing around 4G per day
Backup - 256G incrementing around 2G per day
Trash Size - atm 3.4G gets cleared every hour via Moodle settings
Temp Size - 227M, temp/backup/* gets cleared hourly via manual cron
Total Used - 1.1T
Use% - 59%
Available - 753G
Okay so we're planning on migrating Backup(256G) to NFS as Automated backup is already in "Specified Directory" only mode. But this specified directory is still in the server, once we've changed the location to the NFS, that will be a deduction of 256G or more, which is good. No plans on migrating filedir to NFS as of yet.
256G in backups is only 1 day's worth, with the migration to NFS, we can ramp that up to 2 days or maybe 3. No worries on NFS storage size.
My worry is the server as its available disk space is dwindling.
Let's say there are no failed backups, hence I will no longer need to activate the manual cron that deletes /temp/backup/* every hour.
So automated backup's process looks like this (correct me if I'm wrong).
Auto Backup Starts > backup one course > store in temp/backup > compile > copy to NFS.
My concern is how long will the automated backup task leave the copy of the course in the temp/backup before it gets deleted? Is there a way to delete the temp/backup's copy in real time right after it has been copied to NFS?