EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.
Description of my issue:
Reference Ticket #25484
We are experiencing continued problems with dozens of websites using all of their disk space due to space issues caused by akeeba log buildups and backups that don't complete properly.
I'd like to address one issue at a time since it seems to be a complex blend of multiple parameters.
To summarize what we've done to date:
Despite these changes, after about 10 days, we receive notification that the sites are now over disk quote and the backups are disabled via Watchful. The only files that are building up on the site are the backup files and the logs.
For example, with New Rambler Review, we configured everything to your suggested specs and today we received the notification that the site was over their allotted disk size and that backups were disabled. This site, without any backups or logs uses 257 of 1000mb which should be plenty of space to execute a proper backup. Here's what I found in the backup folder:
The total log files is about 168mb and the two unfinished backups total 350mb. Between the logs and the backups, the site ran out of diskspace to run additional backups or even add new content.
To begin, how do we restrict the number of log files? I keep a close watch on the sites, so I only need up to 5 log files.
Secondly, what else could be the issue?
I've attached the log files from the last five days.
Best,
Dawn
Description of my issue:
Reference Ticket #25484
We are experiencing continued problems with dozens of websites using all of their disk space due to space issues caused by akeeba log buildups and backups that don't complete properly.
I'd like to address one issue at a time since it seems to be a complex blend of multiple parameters.
To summarize what we've done to date:
- Changed our bucket name at Amazon S3 to all lowercase, no special characters.
Changed the part size to 1535.74 with chunk sizes at 1 and big file threshold at 1.
Elected to Resume backup after an AJAX error has occurred
Restricted the number of obsolete records to keep to 5 and the number of days to 5.
Ensured that we have at least 60% of the disk space free (ie: site if 400mb, customer has 1000mb of space).
Despite these changes, after about 10 days, we receive notification that the sites are now over disk quote and the backups are disabled via Watchful. The only files that are building up on the site are the backup files and the logs.
For example, with New Rambler Review, we configured everything to your suggested specs and today we received the notification that the site was over their allotted disk size and that backups were disabled. This site, without any backups or logs uses 257 of 1000mb which should be plenty of space to execute a proper backup. Here's what I found in the backup folder:
The total log files is about 168mb and the two unfinished backups total 350mb. Between the logs and the backups, the site ran out of diskspace to run additional backups or even add new content.
To begin, how do we restrict the number of log files? I keep a close watch on the sites, so I only need up to 5 log files.
Secondly, what else could be the issue?
I've attached the log files from the last five days.
Best,
Dawn
