Support

Hi!

The backup log file points to a number of root causes for the issue you are experiencing. Please follow the steps below in the order presented, trying to take a backup after carrying out each one of them:

1. The first thing you must do is to use the Configuration Wizard button in the Control Panel page to automatically adjust a series of configuration parameters to safer settings. The wizard performs benchmarking of your server to determine those values. It is not always 100% accurate, but the settings it creates are at the very least a good starting point for tweaking them manually. If it seems to get stuck for more than three minutes (180 seconds) the first time you run it, reload the page.

2. Since your PHP memory limit is pretty tight (32Mb) and your site is already using 9.6Mb when the backup start, you may be facing a memory exhaustion issue. Please go to the Configuration page and try the following settings:
- Minimum execution time: 1 second
- Maximum execution time: 5 seconds
- Runtime bias: 50%
This will make the backup slower, but will use much less memory on each backup step, overcoming this potential issue.

3. Check your free space. Akeeba Backup is trying to create an archive with your entire database and all of your site's files; it needs adequate free space to do that. If you don't have enough free space, your host will kill the script in mid-process, making Akeeba Backup's interface throw this error. As a rule of thumb, we propose having about 40-50% of your account's allocated quota free. The more free space the better. Do note that some hosts claim to give you "unlimited" space, or an absurd amount like 100Gb. According to our experience, they mostly lie. On many occasions the host only gave 100Mb or 1Gb of space. If unsure, please ask your host about the real free space you have in your account.

4. I also see that you are using your site's default temporary directory. Sometimes, this is periodically cleaned up, causing an issue with the backup. In order to remove any shred of doubt, please go to Akeeba Backup's Configuration page, find the Temporary directory setting and set it to [DEFAULT_OUTPUT] (all capital letters and remember to include the brackets!). Click on Save and retry backup.

5. You are also using the ZIP archive format it is possible that you run into timeouts. The problem with the ZIP format is that we have to read each file twice. We read it once in order to calculate a "file signature" (properly called a "CRC32 checksum"), then we read it again in order to add it inside the archive. Unfortunately these steps can't be combined and, on top of that, the very slow signature calculation step must be able to run in one go. With larger files and slower hosts this will consistently lead to timeouts. Please use the JPA format setting in the Archiver Engine option of the Akeeba Backup's Configuration page. Do note that the first instruction I gave you (clicking on the Configuration Wizard) will carry out this step automatically for you.

6. Some servers have a very strict CPU usage limit policy. On those hosts, the default behaviour of Akeeba Backup (trying to backup as much data as possible, as fast as possible) may trigger a CPU usage protection. In this case, we have to apply some special settings in the Configuration page to work around that:
- Minimum execution time: 5 seconds
- Maximum execution time: 3 seconds (yes, the maximum IS less than the minimum, it's not a typo)
- Runtime bias: 50%
This will make the backup dead slow (it will take over twice as much time) but will work around the CPU usage restrictions.

If none of these help, please ZIP and attach your new backup log file and tell me which of those steps (1 through 6) you have already carried out so that I can further assist you.

You did not follow all of the steps above. Namely, I can clearly see that you skipped step #5. Please follow all of the steps I mentioned in my previous post. There is a reason I took half an hour to write them down. Unless you follow all of them, I can guarantee that we won't be able to solve this problem ;)

That make sense :) If the updater fails, you get a mix of files from different versions and the outcome is improbable to say the least. I am glad it is working now!