There are some steps on how to replace MariaDB by MySQL:
To save head-scratching and hair-pulling of anyone intending to do this, here’s how it goes: According to MySQL :: MySQL 8.0 Reference Manual :: 2.10.4 Securing the Initial MySQL Account : Installation using RPM packages generates an initial random password, which is written to the server error log. But no, that’s not correct. In the log the password is not output, and instead there are messages that encourage to run a command to change the root password, which does not run, of course, becaus…
Though such replacement may cause issues as mentioned on same page under later post:
Here’s an update for anyone who decides to go down this rocky route: Numerous tests and attempts were made. I’m not a total noob when it comes to Linux, webmin, and Virtualmin, but it really took plenty of effort to get to the conclusions: +----------+---------+-----------------------------------------------------+ | OS | MySQL | Comment | +----------+---------+-----------------------------------------------------+ | CentOS 8 | Ver …
Another replacement steps:
A Virtualmin backup only backs up databases by performing a mysqldump. That is the only way to safely backup a database…the binary files are not guaranteed to work from one version to another, and definitely won’t work going from MySQL to Mariadb. If a restore fails because of the database, you’ll either need to munge the data manually or stick with MySQL. We’re not experts on migrations from MySQL to MariaDB. Mostly, it Just Works, as the two are very nearly compatible. But, they have begun t…
You cannot. We cannot and will not support old installations of Virtualmin (and repos for old installer versions are periodically deleted to prevent people from using old unsupported versions). (And, how the hell did you interpret my comment there as being a suggestion to install an old version of Virtualmin?) Switching to MySQL is covered in several other posts in our forums (be careful about who you take advice from, as well…if it isn’t me or other staff, maybe keep reading for follow ups fr…
https://blogs.oracle.com/mysql/post/how-to-migrate-from-mariadb-to-mysql-80 <<<<
It is worrisome for a layman needing to manually switch from MDB to MSQ. I am already having established site with populated database 10.6.18-MariaDB-cll-lve . My script provider is using MySQL, but told me i may stay on a MariaDB. So that may not be a big problem.
Can anyone please address the main questions in the 1st post of this thread regarding clustering/high availability? I would like to stay away from a load balancing setup with single load balancer (a signle point of a failure) and I think I would need a tutorial. Thank you in advance.