Support

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

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:
We create daily backups and transfer them to amazon s3. Each time back-up creates it creates log files. We keep 30 everyday back-ups and one for each month in amazon s3.

Back-ups transfer correctly but log files are stored in the backup folder and they do not get erased.

We had this issue before: https://www.akeebabackup.com/support/akeeba-backup-3x/Ticket/26546-delete-old-log-files.html

What do we need to configure, to erase log files?

Please advise,
Sandra

Sandra,

I reread #26546. I'm not sure how a perfectly accurate answer could be so completely useless. The retention bug that had just been fixed was part of the problem, but a very small part.

First of all, you don't need the log files at all. You can set the Log Level to none in Configuration. That will turn them off. The down side of that is that we can't diagnose a bad backup without the detailed log. Even with an onscreen error or CRON job email feedback, it just doesn't give us enough information for anything better than a guess. What that means is you have to turn on the log and reproduce the backup - and the problem - before anything useful can be done. That's usually not a big deal.

Second, the log files are not removed based on the quota settings for the backup archives. They are tied to the records in the Manage Backups screen. Those are controlled by the "Obsolete records to keep" setting in the quota section. When the obsolete record is deleted, the log file should be deleted with it. The default setting for obsolete records is 50, which adds up to a lot of log files.

Hi,

Thank you for your reply.

I see there are multiple options for Error Log. Maybe we can choose other options and the error log files will not be so big?
Which one would be still good enough for support?

Please advise,
Sandra

Sandra,

Unfortunately, we need the "All information and debug" level - the biggest one - to diagnose a problem. If you turn the log off, you would have to set it back to All information... and repeat the backup to get a log in case of a problem. The only time this wouldn't work is in the case of an intermittent problem. If you have backups triggered by a CRON job you might have to wait until the job runs again to get the log.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.