Akeeba Backup for Joomla!

Saturday, 03 September 2022 14:35 CDT

trogladyte

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 10MiB, please upload it on your server and post a link to it.

This site has 6 files >=11.7Mb in size (they are all mp4 files though I doubt that matters). Prior to installing Joomla 4.2.2, Akeeba happily backed the site up as is. After installing the latest Joomla, AKeeba did not like these large files. I had to exclude them to have it complete the backup.

I'm not saying there's anything wrong with Akeeba, but it seems more than a coincidence that the "Backup before update" went flawlessly, then the site updated, and then the backup would not complete. As Akeeba hadn't been updated, I'm guessing somethin gin the latest Joomla version caused this issue.

Sunday, 04 September 2022 11:58 CDT

nicholas

Akeeba Engine, the PHP code we use to take backups in all of our backups software, has stopped depending on Joomla's API for listing directory contents, reading file, and writing files since late 2007 when the component was still called JoomlaPack (version 2 is when that change took place) and has not ever used Joomla's API to create backups since it was first released in 2006.

Without a log file I could not possibly tell you what the problem is but I'd suspect either a permissions issue or, more likely, that you are running out of either disk space or available inodes on your hosting account.

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!

Sunday, 04 September 2022 16:16 CDT

trogladyte

I did attach a file, but, apologies, I see I added it as a txt file, not a ZIP. ZIP attached now.

I checked the disk storage and there's 1.19Gb of 2.2Gb used so there should be enough space. As I said, it worked fine doing the pre-Joomla update backup (literally a few minutes before), but, after updating joomla, doing the backup failed with the warning about the over-sized files.

Monday, 05 September 2022 02:17 CDT

nicholas

The log file looks like you may be running out of disc space.

If you are using 1.19 out of 2.2GiB it means that you have about 1GiB of space left for temporary files AND created backup archives. Your backup archive at this point is already 464MiB. Considering that the free space is not updated live (it usually takes a few hours) I am thinking that you are either hitting a space limit OR you are hitting the inode limit of your host.

Can you try taking a scheduled backup over CLI to see if it works? If it does, the problem is that something on your host is removing the temporary file we create between backup steps (i.e. the file can't be read because the host deleted it, not because it failed to be written due to disk space or inode limits).

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