Support

Akeeba Backup for Joomla!

#8813 S3 backup partail failure

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 Tuesday, 01 March 2011 08:50 CST

rbradbury
Joomla 1.5.22
Backup Pro 3.2.3
PHP 5.2.17
MySQL 5.1.55
Troubleshooter guide read!

Hello

I have been successfully uploading my daily backups to Amazon S3 for approx 4 months using 100MB archive chunk size with Akeeba Backup 3.1.2. The task is run using a scheduled CRON job. Host is Heart Internet.

I updated Akeeba Backup on 21 Feb to (I think) 3.2.2 (and again subsequently to 3.2.3 on 26 Feb). Since 21 Feb my S3 backups have failed - typically after uploading just the .jpa file. The only way I can get the upload to run successfully is to reduce the archive chunks all the way down to 5MB (I tried intermediate steps at 50; 25 & 10MB) This is not ideal for a 1.2GB backup due to the large number of individual files.

My host advises no changes have been made to their environment. I have two websites hosted on different webservers and both suffer the same symptoms.

When using 'Backup Now' the following error is generated:

AEUtilAmazons3::uploadMultipart(): [RequestTimeout] Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.
Failed to process file /home/sites/laverdaforum.com/public_html/administrator/components/com_akeeba/backup/site-www.laverdaforum.com-20110301-112933.j01
Post-processing interrupted -- no more files will be transferred

Log file from overnight scheduled CRON job attached.

Would appreciate any suggestions as to how to get larger split archive successfully uploaded to S3 again.

Thanks

Bob

nicholas
Akeeba Staff
Manager
I have just uploaded a new developer release (471 or later) which works around this issue. Download and install it on your site, without uninstalling the previous version. Then, go to your Akeeba Backup profile's Configuration page and click the "Configure..." button next to the Post-processing Engine. Find the "Disable multipart uploads" option and check it. Also set your part size to 100Mb, as it used to be. Save the configuration and take a new backup. The S3 upload behaviour should now be the same as with pre-3.2 versions of Akeeba Backup. Please let me know of your results.

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!

rbradbury
Nicholas - is this a record for a problem to be reported, identified, fixed and tested?

Thanks for the speedy response. SVN 471 installed. All now working again with an upload archive part size of 100MB on a backup archive of 1.2GB Greatly appreciated.

Regards

Bob

nicholas
Akeeba Staff
Manager
That was actually a pretty slow response by my standards, because I didn't see the email notification right away (Thunderbird crashed and wouldn't download emails). I only saw the email notification of your post almost after an hour, when my cellphone synced its email application and notified me :)

I am glad it's working now! The fix will be included in the next official bugfix release of Akeeba Backup.

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!