Support

Akeeba Backup for Joomla!

#35562 Akeeba backup fails on backing up large ucm_history table

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Friday, 27 August 2021 20:17 CDT

kottas

On a site that has a large ucm_history table (37568 rows, 1.3GB size), Akeeba fails on the "database backup" step, with continuous "Error 500" messages while backing up the specific table.

If i exclude that table from the backup, Akeeba completes normally.

I am able to backup and restore the table via phpmyadmin, but why Akeeba fails?

What I've already tried:

- Checking / Unchecking the "Generate extended inserts" option

- Increasing the number of rows per batch

tampe125
Akeeba Staff

Hello,

looking at your log, I suspect your server is running out of space or hitting the inode limit (roughly speaking, the amount of folders and files your filesystem can handle). Step 9 runs for 3 seconds then it gets killed when it tries to create SQL part 1807. If you exclude such table, we create fewer SQL parts and an overall smaller size.

phpMyAdmin works fine because table contents aren't stored anywhere, it simply pipes the data directly to the browser for the download, so it will never "touch" your server.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

kottas

Hello,

It is not running out of space. If it was hitting the inode limit, I'd have a) more serious problems on the server, b) it would fail at the later stages as well when it tries to backup the site files as well.

But just in case, I ran a check.

 

 

tampe125
Akeeba Staff

Ok, let's try another approach. Sometimes we're using too many resources in a small timeframe and our process gets killed. Let's try to slow down te process. Please set the following values inside your backup configuration:

Minimum execution time: 5 seconds
Maximum execution time: 3 seconds
Bias: 50%

Yes, minimum is greater than maximum, that's not a typo. In this way the backup will run slower, avoiding any resource limits.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

System Task
system
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.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!