Here's a simple trick to find large files in your backup set. Search the log file for "large file". It comes up with this result:
<root>/administrator.zip - size: 1940971418
So, basically, something on your site (
not Akeeba Backup) -or yourself- has created a file named administrator.zip in your site's root with a file size of 1940971418 bytes, or 1.80Gb. My educated guess is that you have a CRON job set up on your site which is ZIPping your administrator directory and placing it into that file. Since the default backup output directory is inside the administrator directory, you have an ever expanding backup archive.
Quick example:
- The size of the administrator directory is 5Mb and you install Akeeba Backup.
- You take a 10Mb AB backup archive of your site.
- The CRON job runs and creates a 10 + 5 = 15Mb archive in the site's root.
- You take a new AB backup. Now it's 10Mb + 15Mb = 25Mb.
- The CRON job runs and creates a 25 + 10 + 5 = 35Mb ZIP file.
- You take a new AB backup. Now it's 10Mb + 40Mb = 50Mb.
- The CRON job runs and creates a 50 + 25 + 10 + 5 = 90Mb ZIP file.
and so on and so on... increasing the backup archive exponentially.
Solution:
Step 1. Remove the CRON job which creates that ZIP archive
Step 2. Exclude that ZIP archive, for good measure!
Step 3. Take a new backup and test it. It should restore properly and
not have the administrator.zip file in it.
Step 4. Delete the administrator.zip archive from your site's root
Step 5. Delete your old (bloated) backups
Step 6. Never, ever, create such a CRON job unless you are perfectly sure that you want to bloat your backup archives for no good reason ;)
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!