Akeeba Backup for Joomla!

Monday, 16 December 2013 14:50 CST

user69722

I have a general question regarding the CLI backup. Both the backend and CLI backup work fine. However, I noticed that the same exact profile creates a 62.4MB backup file when executed manually from the backend and the cron job produces a 146.6MB backup file. Again, both are using the same profile.

I have my akeeba tmp directory outside of the web root, so backups of backups are not being made. Also, the backups are stored on Amazon S3, so again, it is not possible that backups of backups are being created.

Any ideas of the large difference in file sizes? I have attached the log in the event you want to look at it.

Monday, 16 December 2013 15:40 CST

nicholas

Are you sure you are using the same profile (#1) in both cases? Apart from that there is no other possible explanation and no, I've been using both of these features on the same sites, day in and day out for years, I'd definitely know if there was such a glaring size discrepancy.

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, 16 December 2013 15:55 CST

user69722

Yes, the same profile #, which in this case is 1. I have another profile, which is 3. It also displays the same behavior. I am not sure why it does this either. I will extract the files and dig through them at some point to try and figure out why. I will let you know if I find anything.

Monday, 16 December 2013 16:08 CST

nicholas

Is it possible to also perform the same test using the JPA archiver engine instead of the ZIP engine?

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, 16 December 2013 16:14 CST

user69722

The JPA test produced the same exact size for both the backend and the CLI backup. Maybe there is a difference in the compression level switch between the CLI and web interface?

I'd prefer to use the ZIP format since it is native in a base OS install.

Tuesday, 17 December 2013 01:39 CST

nicholas

I can't reproduce this. It does not seem to be dependent on the backup archive type (ZIP or JPA). The reason I had you check with JPA is because I wanted to rule out the possibility of PHP's gzip functions not being available in the CLI. Since the JPA worked fine I ruled that out.

Sorry, I don't have an explanation for that. If you tell me that the big and small files do not have any difference and that the same backup profile when switched to JPA doesn't cause a size difference I have no rational explanation as to what is going on. More so when I can't reproduce it on any other system.

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