Support

There seems to be absolutely no reason for the backup being terminated by your host. I suspect that your server has some kind of server protection software installed which mistakes Akeeba Backup for an attack on the server.

One way to work around that, at the expense of making the backup mind-boggingly slow, is using the following settings in Akeeba Backup's Configuration page:
- Minimum execution time: 7 seconds
- Maximum execution time: 3 seconds (yes, the max is less than min, it's not a typo!)
- Execution time bias: 50%

If this doesn't work you should ask your host if they have a CPU usage or memory usage limit, or whether the server will block requests when the same URL is accessed in quick succession by the same IP address. In the latter case please ask them what is the triggering point, i.e. how many time the same URL has to be accessed in how much time for this kind of protection to be triggered. This will help us find a different set of settings for your backup.

OK. If you don't have the information within the next 2-3 hours please note that our support ticket system will be closed for replies from Friday evening to Sunday evening (Eastern European timezone). You will be able to reply to us when it's open again.

The memory limit is already quite big and I could see it from the log file. If it's not your host stopping the backup process, it's something in your computer / browser such as an antivirus or Internet security application. If you are not running such a thing or if the error persists even though you have deactivated your antivirus / Internet security application there are two more troubleshooting steps:

1. Make sure that your computer does not go to sleep mode or disconnect from the Internet and you do not close the browser tab or window where the backup is running. Javascript running on your browser triggers each backup step, checks the server response, updates the interface and repeats this loop until the backup is complete. If your computer goes to sleep, you get disconnected from the Internet etc then the chain of backup steps is broken, the browser reports an error and you get a log file similar to the one you sent us.

2. If this doesn't happen your host is lying. Most likely the first level support technician answering your support request isn't privy to the exact configuration of the server or is not allowed to disclose the measures taken by the host to protect against denial of service attacks. In most cases you can escalate the issue and talk to a real system administrator who will be able to explain why the server kills the backup.

FYI, there is no shared hosting on this planet not enforcing resource limits that is still in business. If they enforce no limits apart from PHP memory limits someone could buy the cheapest shared hosting plan and have the CPU and hard disk on the server work at full capacity, effectively bringing down the server. Having someone from your host telling you that they don't apply any limits is either a blatant lie or they an admission that they are absolutely suicidal and about to go out of business. That's why I'm sounding so sure. Plus the nearly eight years of experience supporting Akeeba Backup (called JoomlaPack back in '06) on shared servers which made me aware of all that stuff to begin with :)