Hi I did the same thing a few years ago, you will have the find the closest next up version of your MySQL to MariaDB. Some jumps are simply too big fore teh upgradee scripts. Mine was a 5.1MySQL going to a 5.5 MariaDB. We moved to 10 about 1 year later. That was all around the time 10 was coming out. You can add MariaDB as a slave to any of your MySQL servers and then do a switch to it as the master. I would recommend that you make it a direct slave to your existing master Steps from memory Make a slave as 5.1 remove 5.1 software Install MariaDB 5.5 Run upgrade scripts to MariaDB Switch to master Obviously somewhat more work around when and how you manage to point your app to the database? I would suggest you run whichever version of MariaDB in your dev and test but not necessarily UAT environments as part of doing this and build a master-slave unit with your current MySQL in say test and then do the switchovers a few times there to confirm your whole process. Cheers Peter On Sun, 28 Apr 2019 at 09:14, Richard Reina <gatorreina@gmail.com> wrote:

I have about five MySQL slaves backing up a MySQL master. The master is rather old and I am planning on migrating to MariaDB. I was hoping I could I create a MariaDB slave that backs up the newest MySQL slave (making it a relay) and then make the Maria slave a master and add Maria slaves until MySQL is phased out. Does this sound like a good plan or would it be better to just create a new Maria Master with dumps and add Maria slaves to it?

Thanks _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

-- Peter McLarty Leader and Technologist 0402094238 http://petermclarty.setmore.com/