Support

Akeeba Backup for Joomla!

#13301 Sugarsync Error?

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, 20 August 2012 08:59 CDT

user11823
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? YesHave I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.6
PHP version: 5.3.8
MySQL version: 5.0.95-community
Host: (optional, but it helps us help you)
Akeeba Backup version: Akeeba Backup Professional 3.6.1

Description of my issue:

I have set Akeeba to upload backup files to a directory on my Sugarsync account. Although it seems that the backup file is uploaded ok, I receive a 500 Error after the backup is finished (see attached screenshot). This confuses me, and I need your help to determin whether I can disregard the error message, i.e. the backup is being transferred ok despite the error message.

I have attached the following screenshots and files to highlight the issue:

- Screenshot of error message
- Screenshot of backup list in Akeeba admin
- Screenshot of uploaded backups in Sugarsync
- Log Zip File

Your advise is much appreciated!

nicholas
Akeeba Staff
Manager
Your backup archive is about 86Mb long. It's too long to be transferred in one go. You have to use a lower Part Size for Split Archives. For more information: https://www.akeebabackup.com/documentation/akeeba-backup-documentation/step-by-step-guides.html#how-to-cloud-backup-basic-config

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!

user11823
Thanks for your advise and sorry if I failed to notice this.

Still, having followed the advise and set the "JPA Archive Part Size" to 20, I still get the same error. The only noticeable change from before is that the backup status in the admin list of performed backups says "pending" instead of "obsolete" - and that only a 20MB part has been transferred to SugarSync.

nicholas
Akeeba Staff
Manager
You may have to try a smaller value. It's not uncommon to see sites where anything over 5 or 10Mb causes a backup failure. In any case it's a good idea ZIPping and attaching the new log file if you want me to be able to give you informed advice instead of an educated guess :)

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!

user11823
Again thanks and sorry for not figuring it out myself. Set it to 5MB and everything sorted.

nicholas
Akeeba Staff
Manager
No problem :) I'm glad it's sorted out!

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!

user11823
Just a short follow up with two questions:

The backup's now finish ok and I get the conformation message. Also, the back up is transferred in 5MB chunks to Sugarsync - 16 parts in all. However, in the admin list of performed backups, the backup is listed as obsolete and as 9.12 MB in size (far smaller than the actual size).

Is this something to worry about?

How is the restore possible. Do I simply upload all parts of the backup to the site and use Kickstart for the restore?

Thanks in advance for your advise.

nicholas
Akeeba Staff
Manager
Can you post the log, please? I'd like to see what gets transferred so that I can give you an informed reply.

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!

user11823
Sure, here it is...

nicholas
Akeeba Staff
Manager
OK, I know what's going on. You're using the "Process each part immediately" option. This moves each part file to SugarSync immediately after it's generated. There is a catch. Since you're also using the "Delete archive after processing" option the part file is being deleted after it's transferred. In the end there are only two parts left to transfer. Akeeba Backup records the size of just these two backup part files. This is a known issue for which there is no workaround. Actually there is a workaround but it can cause backup issues and I've not implemented it. They only drawback is that the backup size column is not reliable in this case.

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!

user11823
Again thanks! Your support is, as always, swift, savvy and comprehensive. As I interpret your reply, the backup uploaded to Sugarsync is ok, but the size displayed in the Akeeba admin is wrong due to the reasons you state. That sounds great. My only concern was to ensure myself that the uploaded backup is reliable and complete!

To restore, do I simply upload all parts (chunks) to my site and run Kickstart?

Thanks alot for your help!

nicholas
Akeeba Staff
Manager
Yes, that's exactly what it is. The backup was uploaded correctly.

As a side note, it's a good idea to perform test restores of your backups. As you said, you just need to upload all your backup archive parts (.jpa, .j01, .j02, ....) to a test server along with Kickstart. Kickstart will automatically detect and extract all parts.

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!