Support

Akeeba Backup for Joomla!

#13469 Backup failing on a large site

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 on Friday, 12 October 2012 18:00 CDT

extramilecomms
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.6
PHP version: 5.3.16
MySQL version: 5.5.25-cll?
Host: UKWSD
Akeeba Backup version: 3.6.0

Log file: http://www.chrometrader.co.uk/documents/akeeba-log.txt

Description of my issue:

Hi. We have a fairly large site at www.chromertrader.co.uk - it's around 6500MB in size, although we were having hosting issues which we thought was affecting the backup. We've now switched to unlimited hosting meaning there's infinite space to play with. Backups are still timing out and receiving an Ajax 500 error.

I've read all the troubleshooters and we are doing everything by the book - I've gone through the configuration wizard countless times, as well as managed the configuration myself to determine the part size outputted, but it never archives it into one complete jpa file as the backup still times out.

We're uploading to a remote server on Amazon S3 but also the site still takes the backups on the server because of the failing error.

Is there anything we are missing? Please see link to log file and attached compressed file.

I look forward to hearing from you. Thanks in advance.

Regards,

nicholas
Akeeba Staff
Manager
The size of the site is not that big. I've seen sites in excess of 30Gb being backed up. 6.5Gb is small change compared to that :)

First, please do upgrade to Akeeba Backup 3.6.3; you are still using 3.6.0. Some minor issues have been fixed in the latest releases.

This looks like a very simple timeout error. Go to Akeeba Backup's Configuration page and set the following:
- Minimum execution time: 1 second
- Maximum execution time: 10 seconds
- Runtime bias: 75%

Please note that if you want a back-end backup to upload files to Amazon S3 you may have to follow the instructions in our troubleshooter, especially the last three paragraphs.

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!

extramilecomms
Hi Nicholas,

I've updated to 3.6.3, changed the min execution to 1 second, the max to 10 seconds and the runtime bias to 75% but still no luck, I'm still getting the Internal Ajax 500 error.

For now please dismiss the Amazon S3 comment, as I know files are being uploaded successfully to that.

I've attached the updated log for you to go through.

Many thanks

nicholas
Akeeba Staff
Manager
Please make sure that the following settings are disabled (not checked) in your Akeeba Backup configuration page:
- Disable step break before large files
- Disable step break after large files
- Disable proactive step breaking
- Disable step break between domains
- Disable step break in finalization
- Set an infinite PHP time limit
then retry the backup. If it still fails, please ZIP and attach the backup log file.

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!

extramilecomms
Hi Nicholas,

I've done all that and it has backed up successfully as two files. One .j01 part size file at 2.0GB and one .jpa file at 1.1GB.

For test purposes, I've uploaded them locally using MAMP for Mac OS X. Somehow, it's having an error connecting to the database giving me an Ajax Internal server error. I've been through all the details on this page (https://www.akeebabackup.com/documentation/troubleshooter/abidatabase.html) twice and tried it with different databases and usernames, toggling between mysql and mysqli and I still get the same result.


I wondered if there's an issue that I have two files to be uploaded, when in previous experience, it's usually all confined into one .jpa file.

It's getting there. I just need reassurance in that we could reupload the site if there ever was a problem.

Many thanks,

nicholas
Akeeba Staff
Manager
Nope, if the archive part files were broken you would have gotten an archive extraction error. You are very well beyond that, so that's not a factor.

The most likely problem is how MAMP handles MySQL databases. Newer versions of MAMP (2.x) require you to use the MySQLi driver and "localhost" as the hostname. Older versions of MAMP require you to use the MySQLi driver, use 127.0.0.1 (but IN NO CASE localhost - it doesn't work!) as the database host name with the custom port appended. E.g. in the typical case of 8889 as the database port you have to enter 127.0.0.1:8889 as the database hostname.

If you have MAMP PRO you can easily click the "Default ports" button in its interface and restart the servers. This allows you to use 127.0.0.1 as the database hostname (best solution).

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
system
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: 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!