Support

Akeeba Backup for Joomla!

#12686 AJAX Errors with Amazon S3 backup

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 Wednesday, 08 August 2012 18:00 CDT

user45373
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes - https://www.akeebabackup.com/documentation/troubleshooter/abbackup.html
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes - https://www.akeebabackup.com/documentation/akeeba-backup-documentation/step-by-step-guides.html
Joomla! version: 2.5.4
PHP version: 5.2.15
MySQL version: 5.1.63
Host: NewSprout
Akeeba Backup version: 3.5.1

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:

I want to have automatic backups to Amazon S3. I previously had this on my Joomla 1.5 site but since the upgrade to 2.5 I haven't been able to get it working completely. After going through all the troubleshooting I managed to get this working manually once, but then when I tried to do the backup via cron it didn't work so I tried manual backup and it's not working again. I'm basically back to square one to sort it all out. I got manual backups working this morning and now am trying to get it to upload to Amazon but keep getting AJAX error messages.

Any help would be great.

Akeeba Backup Log

Thanks.

nicholas
Akeeba Staff
Manager
The backup halts very long before it has any chance to reach the upload to S3 phase. I want you to first try all of the troubleshooting steps in our backup troubleshooting page. I want to make sure it's not something as trivial as, let's say, running out of disk space.

If this doesn't work, try the following setting in Akeeba Backup's configuration:
- Minimum execution time: 1 second
- Maximum execution time: 7 seconds
- Runtime bias: 75%

If this still doesn't work, try this:
- Minimum execution time: 5 second
- Maximum execution time: 3 seconds
- Runtime bias: 50%

If this still doesn't work, try this one instead:
- Minimum execution time: 6 second
- Maximum execution time: 2 seconds
- Runtime bias: 50%

If all else fails, please post back.

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!

user45373
Thanks Nicolas, I've been through the troubleshooting steps and tried your configurations but unfortunately no luck. The closest I got was this morning with min set to 1, max set to 7 and bias at 75 which worked without uploading to s3 first, so I re-ran it after enabling amazon upload and it got part way through before failing. I've included all my attempts below with the configurations as per the file names. Any further help would be much appreciated. Thanks.

Upload partway fail min1 max7 bias75

min5 max3 bias50

min6 max2 bias50

nicholas
Akeeba Staff
Manager
Your server is consistently killing the backup after a while. This really is a server limitation, so let's try working around it by making the backup faster instead of slower:
- Minimum execution time: 1 second
- Maximum execution time: 12 seconds
- Runtime bias: 80%
Then go to Archiver Engine, click on Configure and in the pane which opens set the Part Size for Split Archives to 20Mb.

If this still doesn't work, you'll have to ask your host to relax the CPU usage restrictions on your account.

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!

user45373
Thanks Nic, that worked! This got the backup working when manually backing up from admin and I ran the CRON last night and it worked nicely. Thanks heaps for all your help!

nicholas
Akeeba Staff
Manager
Awesome! You're welcome :)

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!

user45373
Hey Nic, sorry to reopen this one but it's still not quite right. The backup seems to work but the transferring to S3 still isn't working properly as I'm getting an error once the backup completes saying that it couldn't transfer the whole file to s3. Here is the backup log from the manual backup in the backend:

Backend back up to s3

And here is the cron backup log:

Cron backup to s3

Any further help you could be would be much appreciated. Thanks

nicholas
Akeeba Staff
Manager
Please follow our Amazon S3 troubleshooting instructions. You have to check the "Disable multipart uploads" option.

Note: please do not link to uncompressed text log files. Always ZIP them. It makes download faster and helps me help you faster.

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!

user45373
Thanks Nic, the final solution that just worked after many options was to set the part size for split archives to 99.98 MB.

Thanks again!

nicholas
Akeeba Staff
Manager
You're welcome!

Just out of curiosity, did you check the "Disable multipart uploads", too? The reason I'm asking is that I've observed larger archives' transfers to S3 failing when this is not checked.

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!

user45373
Hey Nic, yes this is disabled.. I mean checked.. I mean the disabling is enabled! haha

Disable Multipart uploads is checked, thanks for the follow up. I use this host (NewSprout) frequently so I'll be sure to make a note for these settings.

nicholas
Akeeba Staff
Manager
OK, thank you for the feedback! I had to confirm that the hypothesis on which the troubleshooting article was written still holds true :)

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!

user45373
Hi....This is the owner of the site here. This is still not working. Is it all possible for Akeeba to have a look at the setup in the backend to see what is going on?

Cheers

nicholas
Akeeba Staff
Manager
The previous reply said that it's working. If it's not working, I want to see the log file of the failed backup. Most likely the problem is not related to S3, but a different error occurring at backup (not uploading) time. 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!

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!