Support

This sounds like a max file size issue or a CPU usage issue. Let's try the following setting in Akeeba Backup's Configuration page:
- Find the Archiver Engine parameter and click the Configure button to the right of the drop-down. In the open which opens below please set the Part Size for Split Archives to 5Mb.
- In the bottom part of the configuration page set the following:
-- Minimum execution time: 1 second
-- Maximum execution time: 3 seconds
-- Runtime bias: 50%

If that doesn't work, try this:
-- Minimum execution time: 5 seconds
-- Maximum execution time: 3 seconds (yes, max is less than min, it's not a typo)
-- Runtime bias: 50%

If all else fails, please ZIP and attach your new log file. Thank you!

I see that the backup stops at an arbitrary point while backing up files. This only means one of the following:
- The backup file grows over a certain threshold. We have worked around it with the part size and I see that this is not the problem in this case.
- Running out of disk space. You said that you have enough disk space, but I'm almost sure this not the case. After a failed backup, when you go back to the Akeeba Backup Control Panel there should be some extra log lines written to the log. In your case they are not written, which means that there is not enough disk space (it's the only reason for those lines to never be written). Please check this.
- If you do have enough disk space, the other remaining problem is using too much CPU. We've already tried a conservative setting. An even more conservative setting would be:
- Minimum execution time: 7 seconds
- Maximum execution time: 2 seconds
- Runtime bias: 50%
This will make the backup excruciatingly slow. If that still fails, I am 100% sure that you have a disk space issue. If your hosting control panel insists that you have enough disk space, please contact your host.