Support

On one of my sites that otherwise runs normally, Akeeba runs EXTREMELY slow. We're talking that that it takes about 10 times as long to finish a backup on this site than on similar sites I have elsewhere. All of my accounts are hosted by the same provider: Host Gator.

That said, the backup always finishes successfully -- just incredibly slow.

The only other thing is that the akeeba.backend.log is always 0 on this as well.

Your thoughts?

Thanks,

Doug

Doug,

I have never seen a successful backup with no log. It should be in the same folder as your backup archive.

Please check the timing settings in the configuration screen against a site that runs at normal speed. Are the settings the same?

You can run the Configuration Wizard, that will set the timing settings to optimal for your server. Note that when a backup will not complete or runs into a host imposed limit, we routinely slow down the backup as a work around. That may have happened at some point in the past with this one site.

Hello,

I check against another site and there were some differences in the Advanced Configuration > Database Backup Engine part. Just slight differences. Fine-tuning was identical.

I ran the Configuration Wizard again, and it complete fine, and I did a backup. It seemed a little quicker this time. I will assess the timing.

It completed successfully and akeeba.log has data, but akeeba.backend.log is a 0-byte size. Is that normal?

Doug

No, the zero byte file is not normal. There were some changes to the log function a couple of version ago. The new log saves multiple copies of the log file, so if you do two backups, you should still be able to get to the log from the first, it is no longer overwritten by the second.

Please download Akeeba Backup 4.1.1 and install it twice, back to back, without doing anything in between. Do not uninstall the component, that will cause you to lose all of your settings and possibly your stored backups. This trick usually works around some issues in Joomla!'s Updater.

Hello,

So I did the back-to-back installs of the latest version and ran a backup.

It completely successfully again, but akeeba.backup.log is 0, but there are multiple similar log files -- akeeba.backup.id10.log, for example -- that have data.

Normal?

Doug

I had to go back to school for this one. :-)

That is normal. The akeeba.backup.log file is a "default" file that is used when we need a log file but are not actually doing a backup. It is sort of a trash can. So zero bytes is fine.

The akeeba.backend.idxxx.log files are the actual backup log files. The xxx matches The ID column on your Manage Backups screen. The Restore Point logs work the same way.

Due to limitations in the cli script, only one command line backup log is saved. The command line can't get the ID number properly, so we can't match the log file to the backup.

Whew! Thanks.

Doug

You're welcome!