Akeeba Backup for Joomla!

Saturday, 17 October 2015 03:05 CDT

heinz.riedener

Hi there,

Until today and my update on the newest Akeeba Backup Version my backups with upload to Amazon S3 run without any problems on different instances.

Now the backup runs still without any error message and a proper log:
completed / duration 00:00:34 / status ok / 25.40 Mb

but the file on Amazon S3 has only 10.00 Mb (before it was 25.8 MB and there was no change within this website). And it is not the only one with the same resultat. And all of those backups are startet manually without any other action during the backup

Thanks for any help!

Best regards
Heinz

Monday, 19 October 2015 01:50 CDT

nicholas

Now the backup runs still without any error message and a proper log:

This sounds like two unrelated configuration errors which do not affect the execution of the backup at all:

1. You are redirecting the standard output to /dev/null in this CRON command line. This means that the script's output is not visible and is not logged anywhere. Try removing the > /dev/null part from your CRON command line.

2. If you get no Akeeba Backup log file you have set the Log Level to None in the Configuration page of Akeeba Backup. Please go back there and set the log level to "All Information And Debug". Then retry backing up. Go to Manage Backups. There should be a View Log button next to the backup attempt which will let you view and download the log file. Even if you cannot view the log file click the download button all the same. You will get a .txt file with the log.

but the file on Amazon S3 has only 10.00 Mb (before it was 25.8 MB and there was no change within this website). And it is not the only one with the same resultat. And all of those backups are startet manually without any other action during the backup

I believe this has to do with a bug regarding part sizes that are an integer multiple of 5. Please try using the latest dev release from https://www.akeebabackup.com/download/developer-releases/akeebapro/rev494aaa8.html I thank you in advance for your 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!

Monday, 19 October 2015 13:06 CDT

heinz.riedener

Hi Nicholas,

#1
All my backups initiated with CronJobs are running correct and complete - no problems there.
All my backups started via joomla backend are running correct and complete - but only transfer the 10 MB to the Amazon S3 account!

#2
As I have access to all backup log files I did not do those actions!

#3
I downloaded the com_akeeba-rev494AAA8-pro.zip and run the backup once before and once after installation. Here the results:
id269 00:01:00 25.40 Mb run successfully - 10 Mb saved on Amazons S3 account
id270 00:00:36 25.43 Mb run successfully - 5 Mb saved on Amazon S3 account
log files attached!

Hoping that this helps to solve the problem.

Best regards,
Heinz

Monday, 19 October 2015 13:08 CDT

heinz.riedener

2nd try with the attachement (without spaces within the filename)

Monday, 19 October 2015 13:09 CDT

heinz.riedener

once again

Tuesday, 20 October 2015 01:50 CDT

nicholas

Can you please ZIP and attach the log file from the CRON job which you said it works fine?

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!

Wednesday, 21 October 2015 00:56 CDT

heinz.riedener

That are three examples of cronjob based backup logs - hope that helps!

Wednesday, 21 October 2015 00:58 CDT

heinz.riedener

Would you please remove all the log files from public view after you copied those information? Thank you!

Wednesday, 21 October 2015 02:16 CDT

nicholas

Dear Heinz,

I need the backup log, not the output of the CRON script. Please log in to your site's back-end. Then go to Components, Akeeba Backup, View Log. In the drop-down list there should be an option called "Command-line". Select it. When the page reloads you should see a log file of the latest CLI backup attempt. Click on the blue "Download log file" button. This will download a .txt file to your browser. Please put it in a ZIP file and attach it with your next reply.

Regarding the visibility of the attachments you post here, please do note that we take your privacy very seriously. To this end we've taken two very important privacy measures which apply even to public tickets like this one:

Attachments are only visible by the owner of the ticket (you) and the support staff (us). Anyone else coming on the page does not have access to the attachments.
Attachments are automatically purged from our server after 30 days. According to our experience this covers the needs for virtually all of the support cases we've ever dealt with.

So don't worry. The attachments are treated in confidence.

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!

Wednesday, 21 October 2015 03:03 CDT

heinz.riedener

Sorry but there was no output. I had the rule to log only error and warnings. Now I changed it to log all the information and will provide you tomorrow morning the respective log.

Wednesday, 21 October 2015 03:33 CDT

nicholas

All right. 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!

Thursday, 22 October 2015 00:55 CDT

heinz.riedener

That's last nights log of the CLI version which works correct with the transfer to Amazon S3 (but it's not the same installation we have troubles with limited data transfer)

Thursday, 22 October 2015 01:31 CDT

nicholas

Now you confused me. The CLI log you sent me is from a different site than the one you have a problem with?

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!

Thursday, 22 October 2015 02:21 CDT

heinz.riedener

Maybe I was not clear enough with my first entry. I'm using Akeeba Backup for different sites and those which run with a cronjob are working correct. All others where I am not able to use cronjob (based on the providers rules) and I run Akeeba Backup weekly manually via backend have the same problem with the in the profile integrated data transfer to Amazon S3.

Sorry not to be very clear from the begin!

Thursday, 22 October 2015 04:15 CDT

nicholas

You were unclear and I ended up trying to provide you the wrong solution to the wrong problem.

Please start a new ticket about a SINGLE site with this issue. Be very specific about what you are trying to do, what kind of error you get and exactly how you run the backup (back-end, front-end legacy mode, JSON API, CRON job). I will also need a log file of the ONE site you are requesting support for.

I am closing this ticket because it's now a convoluted mess that will only serve to confuse us. Do keep in mind that due to the volume of support requests we receive we have to read the ticket when you reply to understand the context of your replies. As it is right now, this ticket will lead to more confusion. That's why I'm closing it and asking you to file a new one with accurate information about JUST ONE site that I'll be helping you with. 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!

Support