Support

Akeeba Backup for Joomla!

#8683 Error Message: Backup Failed

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Monday, 25 October 2010 23:59 CDT

user8329
When I run my back up everything seems to be going okay until the very end and then I get this error message that the "Backup Failed" and that the last message was "AJAX Loading Error" and that there was an "Internal Server Error". I checked the log files but I don't see anything that stands out. I'm putting the output of my backup on Amazon S3 and when I look at my bucket, it appears to be there.

So, while the backup seems to be working I'm very confused and concerned by this error message. I am running Akeeba Backup Professional 3.1.

Any clues what could be wrong?

user8329
Also, here is a link to the Log File

nicholas
Akeeba Staff
Manager
Indeed, your file was transferred correctly to S3, but a timeout happened when trying to proceed to the next step (which simply displays the "Backup is complete" message). Here are the log lines which tell me that:
INFO    |101024 19:03:35|Post processing file /administrator/components/com_akeeba/backup/(filename redacted).jpa
INFO    |101024 19:13:13|Successfully processed file /administrator/components/com_akeeba/backup/(filename redacted).jpa

As you can see, it takes almost 10 minutes to upload the file, but Akeeba Backup considers any step taking more than 3 minutes to be an indication of a failed backup. There are two things you can do:
1. If you don't mind getting that error at the end of the backup, you have to do nothing. As long as the log file includes the "Successfully processed file" message the file is complete and transferred to S3. The good thing with this approach is that you have 1 archive file per backup, while the downside is that you'll keep on receiving this error message at the end of the backup process.
2. You can set the Part Size for Split Archives to something lower (say, 20Mb or even lower, depending on your server) as explained in the documentation. This will split your backup to many files, each of which will take much less time to upload and avoid the false alarm at the end of the backup. The downside to this approach is that each backup now consists of several files and managing them might be more complicated. The good thing is that you won't be receiving the error at the end of the backup process.

Both approaches work equally good, so it all comes down to a matter of preference. There is also a reason why we have the 3 minutes timout condition check hardcoded in Akeeba Backup's interface. Apache, the web server, will close the HTTP connection to the browser after 3 minutes, no matter if the script is still running. As a result we can't pretend that everything is fine despite taking so long to get a response from the server (we won't get a response!) and this is why the documentation suggests that you use archive splitting.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!