Akeeba Backup for Joomla!

#23643 Cannot backup database - Table '.xxx_etc' is marked as crashed and last (automatic?) repair failed SQL=SHOW CREATE TABLE `xxx_etc'

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 user84825 on Wednesday, 04 November 2015 09:29 CST

Wednesday, 04 November 2015 03:59 CST

user84825

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

Description of my issue:

ISP had a crashed server, after restore, we are unable to take backup of our Joomla 2.5.28 website using latest akeeba backup pro 4.1.2 for J25x
Cannot backup database - Table '.xxx_etc' is marked as crashed and last (automatic?) repair failed SQL=SHOW CREATE TABLE `xxx_etc'
we repaired/optimized the database ALSO with the help of our ISP

MariaDB [(none)]> repair table xxx_yyy.zzz_banner_clients;
+-------------------------------------+--------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+-------------------------------------+--------+----------+----------+
| xxx_yyy.zzz_banner_clients | repair | status | OK |
+-------------------------------------+--------+----------+----------+
1 row in set (0.12 sec)

But error remains the same. THEN I copied the table (named it xxx_02) and removed the table.
I then uninstalled and reinstalled Akeeba Backup Pro 412
Although the table was removed, I still get the same error.

How can we work around this ?

Wednesday, 04 November 2015 04:26 CST

tampe125

Hello Roland,

what we report is the exact error the database server is outputting.
There's nothing we can since, since the don't have db and filesystem root access. It seems that table files are gone, but it's still listed inside the INFORMATION_SCHEMA.
The only thing you can do is to exclude that table from the backup.

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!

Wednesday, 04 November 2015 09:29 CST

user84825

Thank you for your prompt response.
Situation is solved by our ISP - it appears that there is a ghost database with the exact same "signature"
At least you gave me the weaponry needed to question things and get it solved.

Support