Support

This is more of a question than a problem.

I brought Akeeba backup a while ago, and have today "gone live" with using it. However, the backup file sizes are vastly different from what I was expecting.

For example, my previous backup program (X-Cloner) backup up my entire site, plus database, and the file size is 258,958kb.

Akeeba has backup up the same but at 186,633 kb.

So, is this a better use of compression, or has it not backed up all my site ? - I really don't want to restore to a new "test" site just to find out.

I have looked through the logs, but I'm not skilled enough to answer what is probably a simple question!

You need to increase your paranoia. An untested backup is a very dangerous thing. It is pretty simple to set up a local LANP/WAMP/MAMP server and do occasional tests. You'll sleep better.

You can search for "skipping" in the log to see what was not backed up. These are all standard things to skip, tmp, cache, log, backup, system files, etc. The finder tables for your site's full text search are also skipped. Backup compression is not a priority, large files are just stored, not compressed at all. This is required by the time limitations in PHP.

I can't comment on the size difference between Akeeba and XCloner. I've never used XCloner so I don't have any idea of the inner workings. If it backs up the various folders that Akeeba skips automatically, that could easily account for the size difference.

Thanks, but I think my question was misunderstood.

I would not leave a backup untested, I was asking about compression and file sizes.

However, I think you have explained this by it not backing up temp and cached files - thanks

I really don't want to restore to a new "test" site just to find out.

That was the reason for my "untested" comment.

Yes, if XCloner doesn't auto skip the files and folders that do not need to be backed up, that accounts for the size difference.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.