Akeeba Backup for Joomla!

Friday, 08 April 2011 13:55 CDT

user9936

I have a backup with post-processing upload to Amazon S3. Whenever I run it only the .jpa file gets uploaded to S3, but not the other parts of the archive (.j01 .j02 etc.). The log file ends without errors:

[110408 13:26:20] Finalizing archive 
[110408 13:26:22] Initializing post-processing engine 
[110408 13:26:24] Beginning post processing file /home/chicago/joomlapack/FullSite-WithPhplist-NoAudio-www.chicagochurch.org-20110408-181953.jpa 
[110408 13:26:25] Finished post-processing file /home/chicago/joomlapack/FullSite-WithPhplist-NoAudio-www.chicagochurch.org-20110408-181953.jpa 
[110408 13:26:25] Post-processing has finished for all files

I have tried large (1 GB) and small (5 MB) part sizes and the result is the same. Any suggestions?

Akeeba 3.2.5
Joomla 1.5.22
PHP 5.2.15
MySQL 5.1.52 ?
Host: HostGator

Friday, 08 April 2011 15:59 CDT

nicholas

Can you please ZIP and attach your entire backup log file so that I can see exactly what is going on? Thank you!

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!

Friday, 08 April 2011 16:05 CDT

user9936

Here are two logs with different part sizes.

Friday, 08 April 2011 16:21 CDT

nicholas

I need you to set the log level to "All Information and Debug", retry backing up and attach the new log file here. You have currently set the log level to "All Information" (but without debug) which really tells me so very few things about what's going on that makes it impossible to understand if the problem is in the file packing algorithm, the backup record management, the processing engine, wrong setup of the processing engine or a server issue.

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!

Friday, 08 April 2011 17:56 CDT

rbradbury

Nicolas - I have experienced the same problem following upgrade to 3.2.5 yesterday - log file attached.

Joomla 1.5.23
PHP 5.2.17
MySQL 5.1.56

Had a similar problem with an earlier update which you quickly resolved - see

https://www.akeebabackup.com/support/forum/topic/27369-s3-backup-partail-failure.html

Regards

Bob

Saturday, 09 April 2011 03:18 CDT

nicholas

@rbradbury According to your log file there was only one backup part generated, with a .jpa extension and it was uploaded correctly to Amazon S3. Can you see that file in your S3 account?

@all: I did some thorough testing today and I replicated this issue. If you have split archives, only the last part is being post-processed, if and only if you don't use the "Process each archive part immediately" option. I am going to fix that and publish a new release today. Stay tuned and thank you for your excellent feedback!

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!

Saturday, 09 April 2011 05:09 CDT

rbradbury

Hi Nicholas - yes, can confirm the .jpa file was successfully uploaded to S3.

Bob

Saturday, 09 April 2011 05:40 CDT

nicholas

Version 3.2.6 was just released, addressing this issue. Please upgrade and report your results. Thank you!

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!

Saturday, 09 April 2011 09:37 CDT

rbradbury

Unfortunately I cannot get the update to work. The automated process (used OK to update to 3.2.5 from 3.2.4) from within AkeebaPro reports
ERRORNOTFINDXMLSETUPFILE
Invalid package type. The update can not proceed.

Trying Joomla!s Extension Manager also fails (site FTP enabled)
* JFTP::mkdir: Bad response
* JFTP::mkdir: Bad response
* JFTP::write: Bad response
* Unable to write entry

Saturday, 09 April 2011 09:41 CDT

nicholas

You can always download the installation ZIP package from https://www.akeebabackup.com/latest and install it using Extensions, Install/Uninstall without uninstalling your existing version.

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!

Saturday, 09 April 2011 09:52 CDT

rbradbury

Yes, tried that and got the error shown above....

Saturday, 09 April 2011 14:49 CDT

nicholas

That is a Joomla! issue with the setup and/or permissions of your tmp directory. Please follow installation troubleshooting instructions first. If this doesn't work, 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!

Saturday, 09 April 2011 16:20 CDT

rbradbury

Hello Nicholas

Yes, thanks for confirming what has been a nuisance for some time. In summary, the problem appeared to be some incomplete or 'hanging' installation(s) of modules that was preventing the latest Akeeba BackupPro update from working (I had already tried turning FTP on & checked tmp file permission was OK). Deleted some - hopefully superfluous! - files that had already done their work in loading modules. The real confusion for me was that the previous Akeeba update had worked fine.

Anyway - to business - I can confirm that 3.2.6 works fine and backs up an 850MB website in 100MB chunks to S3 correctly. Thanks again for the quick fix.

BTW, I note in your earlier reply you commented

only the last part is being post-processed, if and only if you don't use the "Process each archive part immediately" option

Is it worthwhile switching to this option?

Regards
Bob

Saturday, 09 April 2011 16:23 CDT

nicholas

OK, it's good to know that everything's working now!

Regarding that option, yes, it's worth turning on. It will conserve disk space, as each part will be transferred to S3 as soon as it is generated. The only drawback is that if the backup crashes or the post-processing crashes, you'll end up with some leftover files in your S3 account. IMHO, that possibility is very low compared to the benefits of not having to store all of the backup archive parts to your server prior to uploading it to S3.

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