Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? Yes, all except the file type specific ones and the database dump and the restoration troubles one
Have I searched the tickets before posting? yes and google
Have I read the documentation before posting (which pages?)? most of the akeeba backup ug specifically the parts on configuration and scheduling backups
Joomla! version: 2.5.8
PHP version: 5.3.17
MySQL version: 5.1.66
Host: bluehost
Akeeba Backup version: 3.6.9
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:
Hi, I have scheduled backups set up with native cron for this client. It works fine and all good taking a backup weekly for them.
Today when I went to update Joomla to 2.5.8 (I took a backup first) I noticed that the command line backup files are much larger than the backend backup files. I first searched the user guide looking for something that I may have missed or some reference to why the files via command line might be much larger. I also did a google search - yet, who knows if I'm putting the right search criteria in to get the correct return. I also read almost all of the links that you so nicely gave me above the ticket once I put in the topic.
Attached is a zip file with the logs for both backend and command line. I hope I did it correctly for you. If not, let me know what I need to do differently. Hopefully that will help you to understand. I'm just looking for why the file size of the command line backups are so much larger than the backend backups and if I've screwed up, then I certainly need to fix it and would appreciate your assistance. Looking forward to seeing you next week at JWC...and thanks in advance for your assistance.
jenn
