Support

Akeeba Backup for Joomla!

#18216 New ALICE analyzer error messages -MySQL version compatibility

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 nicholas on Thursday, 21 November 2013 02:10 CST

erixis
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:

Just trying out your new ALICE log analyzer. Not noticing any problems, but wanted to see what ALICE could do.

I got the following errors:

Database version too old. Detected version: 5.0.37-standard
Akeeba Backup supports only MySQL 5.0.47 or later, PostgreSQL 8 or later and Microsoft SQL Server 2012 or later

Number of tables being savedError
You are trying to backup too many tables. Please avoid backing up different Joomla! installation at once.
You can exclude non-core tables using the following regular expression: !/^#__/


Now, I've read that MySQL 5.047 is recommended, and I certainly understand using the newer versions is probably safer, but my question is: Is this incompatibility going to prevent a restore in the event I have to, or is it just that the newer version is a more reliable version?

Secondly, about the Number of Tables Saved Error - This is just a standard Joomla install, with not a huge number of third party add ons, and I don't have Akeeba set to backup anything but this one site and DB, so what would make this error occur and how do I fix that or do I need to?

Just wanting to fix these issues before I find out after a disaster that I can't restore.

Thanks for your excellent software and the hard work you put into it!

Eric

nicholas
Akeeba Staff
Manager
> Now, I've read that MySQL 5.047 is recommended, and I certainly understand using the newer versions is probably safer, but my question is: Is this incompatibility going to prevent a restore in the event I have to, or is it just that the newer version is a more reliable version?

A question of reliability mostly. Moreover, on severely old versions of MySQL we can't guarantee that the backup of some special table entities (procedures, functions and triggers) will work. 99.5% of our clients are not affected as they are not using them. If you don't know if you are using them the answer is you don't; you would definitely know if you'd use them!

> Secondly, about the Number of Tables Saved Error - This is just a standard Joomla install, with not a huge number of third party add ons, and I don't have Akeeba set to backup anything but this one site and DB, so what would make this error occur and how do I fix that or do I need to?

This should be normally triggered if we detect other tables in the same database with a different prefix than your site's. Perhaps you have some old tables with a different prefix?

> Just wanting to fix these issues before I find out after a disaster that I can't restore.

ALICE is designed as a post-mortem tool, not a preventive maintenance method. It's good at figuring out why your backup died, not tell you how to prevent it from dying.

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 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!