Akeeba Backup for Joomla!

#36393 Extraction Errors

Posted in ‘Akeeba Backup for Joomla!’
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
PHP version
Akeeba Backup version


Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
Hosting Provider: A2-HOSTING

Running Kickstart 7.0.4 and getting errors.
I tried several different Max/Min settings and the best I could get is that if fail at the end.
This is shared hosting and I do not know what OS ISP is running. Obviously they claim the problem is in the script.

I have run kickstart many times on other servers and there were no issues. I also tested extraction locally on XAMPP and it runs fine.  Extracting locally  could be one time only option. It takes forever to transfer entire site and it is absolutely not a solution for me.

Do you have any other ideas whet else I could check ? Doe kickstart version matter ? PHP settings ? etc.
This is second site I cannot restore on this same server. The first one was J3 and this one is J4.

Akeeba Staff

A2 is running Linux per their site.

One possible problem that you are running out of free space or inodes (the latter is roughly equivalent to the total number of files and directories). You need enough space for the backup archive, the extracted files and the database data.

The other possible problem is that they have a request rate limit. On Apache they are usually implemented with mod_evasive (no longer maintained), mod_security2 or mod_qos. They reject requests if they are coming “too fast”. On the database side you can set up MySQL or MariaDB to limit the maximum number of requests in a given amount of time.

I assume that you have a problem extracting the archive which would be the former rate limit — on the web server. You can try to work around these limits with the min/max settings. I'd use super conservative settings: maximum execution time 3 seconds, minimum execution time 8 seconds. This limits the requests to 7 requests per minute and is dead slow. If even that does not work, ugh, I mean you CAN extract the backup archive locally and upload all the files, then access /installation/index.php on the live server after having uploaded all the files.

Still, you'd probably have a hard time restoring the database because of the request rate limit and/or database query rate limits.

Another issue you may have — I do not know if they actually implement something like that — is file scanning on creation. Joomla and its extensions contain many file which may be misidentified as malicious by a naive file scanner. We've seen some hosts which automatically kill PHP scripts or delete fails if the file scanner misfires.

None of these issues are, of course, issues with our software. They are server configuration issues and can prevent you from restoring your backup archive.

Start with the min/max settings to rate limit the requests. If it still fails, check the free space. If there's enough free space contact the host and say, hey, you are clearly rate limiting requests, how am I supposed to restore AN ENTIRE SITE if you don't let me run the script which extracts the files and runs the database queries to populate the database? The first level of support will be useless (they have no authority, they are just there to tackle the easy support requests), so don't be afraid to escalate to second or third support tier.

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!

System Task
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.