Support

Can you please ZIP and attach the backup log file? I don't want the failed backup archive (which you seem to have linked to above), I want the log file. In order to obtain that, please go to Akeeba Backup, View Log, select the Back-end origin, click on Download log file, then ZIP the downloaded .txt file and attach it to your next reply. It will help me understand what is going on.

Sorry for the delayed reply. I saw your email yesterday night but my brain was too fried to let me write a sensible reply.

I actually don't see any problem in the backup. It seems that either your network connection was lost or your host killed the backup.

If you are on a wireless connection (Wi-Fi, 3G) please try using a wired connection. I've seen all crazy things happening, from microwave ovens killing a Wi-Fi connection long enough to trigger a backup error to 3G connections showing as connected but intermittently transferring no data for quite a while. Nothing beats the stability of a wired connection, unfortunately. Also make sure your computer doesn't go to sleep.

If this doesn't help (which is the most likely outcome) then we're just witnessing another round of GoDaddy screwing up sites, like they always do... GoDaddy will kill off PHP scripts, like the backup script, if they consume too much CPU-seconds over a finite period of time. The problem is that their servers are so abysmally slow and overcrowded that this limit does get met when backing up sites, but not always. It depends on the activity of the rest of the sites on the server. One way to work around that is having the backup script do a small amount of work, wait without doing anything for a long time and so on. This will make the backup slower than a snail caught on molasses but has the potential to work. In order to do that, try the following configuration settings in Akeeba Backup:
- Minimum execution time: 7 seconds
- Maximum execution time: 3 seconds (yes, the maximum is less than the minimum, this is not a typo)
- Runtime bias: 50%

My suggestion: please migrate your sites to a real host. GoDaddy is an overpriced, underperforming, overcrowded joke of a host – and a target for hacker groups due to their stance against the freedom of speech in Internet (as witnessed by the last DNS blackout a few days ago).

No, there is no such thing in the php.ini. PHP doesn't have such an option.

I mean: PHP doesn't have such an option built in by default. There are third party patches and CGI wrappers which impose CPU usage limits. These are not controlled by php.ini.