Support

Akeeba Backup for Joomla!

#29178 DB

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 Wednesday, 14 March 2018 18:17 CDT

Saturday, 10 February 2018 13:34 CST

pauloneal
Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

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:

my DB is Server version: 5.6.36-82.1-log

When i tried to do a restore it says it needs to be version 5.7 - How come?

Ive now had to downgrade. Is this correct?

Monday, 12 February 2018 01:36 CST

nicholas
No, we never tell you to downgrade your MySQL version. We don't even have any message telling you anything even remotely similar to that. I have no idea what message you got but it's not coming from our software.

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!

Monday, 12 February 2018 08:04 CST

pauloneal
No, i mean, ive had to downgrade my version of Akeeba so that it will work on my server!

Monday, 12 February 2018 08:14 CST

nicholas
It still doesn't make sense to me since I'm developing and testing Akeeba Backup on MySQL 5.6. I am pretty sure I couldn't do either if it complained it needs MySQL 5.7 :D

Also, I insist that there is no message asking you to upgrade MySQL. Can you at least provide a screenshot of the message so we can see what you see?

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!

Monday, 12 February 2018 08:17 CST

pauloneal
I will update as soon as i get the message again. Ive since downgraded Akeeba so i can run the restore.

Ive no need to restore again at the moment. Lets hope then this was just some random glitch and i never see it again.

Thanks

Monday, 12 February 2018 08:31 CST

nicholas
Why did you downgrade to restore a backup archive?! The restoration script is included in the archive. The Akeeba Backup version you have installed on your site is completely irrelevant. If you need to extract the backup archive and you cannot access Akeeba Backup you can most definitely use Kickstart.

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!

Monday, 12 February 2018 08:51 CST

pauloneal
i downgraded because of this error i got that said something about XXXX was too long. When i googled the error, it said that only SQL v5.7 could handle this request.

I was needing to get the site back up quickly, so i downgraded, made a new backup and the restore worked straight away.

Sorry i dont have the exact details

Monday, 12 February 2018 09:33 CST

nicholas
OK, now you are making sense. But no, MySQL 5.7 has nothing to do with it. Also, your problem was with the restoration which is irrelevant to the version of Akeeba Backup you have installed.

Your problem was that you had an old table in utf8 collation whereas your site is using the utf8mb4 collation. To cut a long story short the solution is to deselect (clear the checkboxes of) the options Force UTF-8 collation on database and Force UTF-8 collation on tables in the restoration's Database Restoration page. Note that these are not selected by default.

So of course this issue won't happen again when you upgrade Akeeba Backup since the problem stemmed from you checking two optional boxes in the Database Restoration page and the issue had to do with the data you had backed up :)

And that's why we ask for exact error messages. It would have saved us more than an hour of wasted time between us and you'd have gotten a reply much easier. Please, don't give us your misinterpretation of the situation as facts. You did NOT see an error message telling you to upgrade MySQL. By claiming that falsehood as a matter of fact you are derailing our troubleshooting process. Again, that's why we ask for exact error messages; it prevents wild goose chases (I had to read every. single. message you could have possibly seen and audit the installation and restoration code for MySQL version checks - that's a full hour I spent this morning before replying to you). Thanks.

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!

Wednesday, 14 March 2018 18:17 CDT

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.
Edited by on 2018-03-14 18:17 CDT

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!