DO NOT transfer from MariaDB to MySQL

[mencargo]

We are trying to migrate from a 60+ account server:
CentOS 7.9 cPanel 106 MariaDB 10.3
To a new server with:
AlmaLinux v8.7 cPanel 106 MySQL 8.0
Assuming that since MySQL is the default option for new cPanel installs and MariaDB option is no longer present, it would be a better tech stack for cPanel support in the long term. Thoughts?
However, the Transfer Tool throws 90+ warnings for DB restores
Would an upgrade to MariaDB 10.5 or 10.6 be more compatible for backup/restore?
Any recommendations?
Log example:
RESTORE: Account “###”: Warnings
Removed empty DB for failed restore of “###”.
The system has saved the database archive data in the directory “/home/###/cpmove_failed_mysql_dbs.###”. You may use this directory’s contents to restore your data manually.
Removed empty DB for failed restore of “###”.
Failed to write to DBI subprocess: Bad file descriptor

 

[quietFinn]

AlmaLinux v8.7 cPanel 106 MySQL 8.0
Assuming that since MySQL is the default option for new cPanel installs and MariaDB option is no longer present, it would be a better tech stack for cPanel support in the long term. Thoughts?

It's possible to select MariaDb when installing cPanel:

Customize Your Installation | cPanel & WHM Documentation

This document describes how to customize your cPanel & WHM installation.

docs.cpanel.net

 

[mencargo]

It's possible to select MariaDb when installing cPanel:

Customize Your Installation | cPanel & WHM Documentation

This document describes how to customize your cPanel & WHM installation.

docs.cpanel.net

We went with MariaDB in the first place for performance and to support the more open source project, but I assumed that was better to migrate back when I noticed that it's no longer really "select MariaDB when installing", like it was in previous cPanel versions, it's now a "pre-configuration".

They deliberately removed that feature and made MySQL the default, no way around it after install, the user will face the problem and need to reinstall.
For me that's a clear statement, but the more I read about it, it seems they just made bad choices.

Like the "warning" of not being able to restore a DB from an account in Transfer Tool, that's an error, huge, not a warning.
More now that the "Live Transfer" is the default option, with no easy way to disable it in bulk.
We got 100+ websites live, after the transfer, 90% of them didn't work.
We did a rollback using this script to "unsuspend" all accounts in the previous server.
Terrible experience.
We will probably reinstall with MariaDB instead of trying to fix this, and keep testing cPanel alternatives.
(several with webmin and one with cyberpanel, still using cpanel for shared hosting servers)

 

[quietFinn]

More now that the "Live Transfer" is the default option, with no easy way to disable it in bulk.

It's possible see:

 

[mencargo]

It's possible see:
View attachment 81169

Didn't notice, thanks. And it should automatically cancel the "Live Transfer" for an account if it fails to restore a DB on it.

 

[JoseDieguez]

yep, we saw something like this 1 or 2 weeks ago, migrating around 1.200 accounts. an easy transfer, ended up on a full weekend of work.

Worst part, Cpanel bugs. transfer log has 99% lines that are a bug not fixed by Cpanel staff yet.
from the other 1%, 99% of it, are warnings that you can totally ignore.
so you have to pick with your fingers the warnings (because according to Cpanel a website without a database is a warning, not an error or failure), and start working on that acc.

 

[slim]

Is this still an issue? I spun up a new server to replace and old one and started transferring sites - They seemed to go ok, but I don't want to get 50 or 100 sites in and discover an issue. Im going from a MariaDB 10.3 box to brand new MYSQL 8 cPanel box.

 

[cPRex]

@slim - if you're already transferring it's a bit late to worry about it :D

I'd check a few sites and see if it goes well.

 

[slim]

I reversed course. Got rid of mysql8 and installed Mariadb10.6.

 

[Steini Petur]

Hi,

They deliberately removed that feature and made MySQL the default, no way around it after install, the user will face the problem and need to reinstall.
For me that's a clear statement, but the more I read about it, it seems they just made bad choices.

It's not exactly true, you can. Im not sure if this can apply here if you have gone too far, but you can re-do your MySQL to MariaDB on the new server and re-migrate. They do offer a way to start with MariaDB by creating a config but I ran into this issue after installation, Just to leave it here

How to Downgrade MySQL 8.0 to MariaDB 10.3 (Fresh install)

forums.cpanel.net

I showed in this post further down a clean way of getting rid of MySQL 8, for MariaDB 10.3 which will be applicable to other MariaDB versions post-installation of cPanel with MySQL 8, it's tried and tested, and it's clean. I did this on a few servers because I kept forgetting about the "create profile" by cPanel before the cPanel start and since they don't offer this, we just MAKE it happen.

It is 100% safe, I guarantee you this, I have it memo down because I had to create this way because cPanel can't officially support it.


PS: This is not to be done on a server with MySQL databases, already, you will be moving them to /var/lib/mysql to mysql.bak essentially, so this is contingent on you running the server Migration again, once you have set the MariaDB version you would like instead of MySQL 8, trust me, the headache of attempting to fix db's post migration Maria to Mysql is a HELL of a headache versus, set the MariaDB and REMIGRATE all accounts. Just my two cents.