Comments - Migrating MySQL 5.5 Windows to MariaDB 10.x on new Windows server
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
You should be able to set up your new server as a replica and then switch without the downtime, if your database takes a while to backup and restore with mysqldump this is likely a better way as you should be able upgrade to 10 with about 10 minutes downtime. I am assuming you are running innodb tables, it makes a difference to the impact to your system Step 1 install mysql 5.5 on your new server and restore a backup, using percona xtrabackup or take your dump and restore which you use to the new server and enable replication
Upgrade the slave to 10 Straight binary replacement and run mysql_upgrade
When you are happy it is working and your data is all good then you can make your replica the master and switch your app to point to your new server. Stop your application On 5.5 server issue FLUSH LOGS; Steps to switch on slave(aka new server) 1) STOP SLAVE; 2) RESET MASTER 3) remove the read only setting SET GLOBAL READ_ONLY=0; 4) Point your app to the new master 5) Log on to your old master server and shut down the database 6) put read-only=1 into the old server cnf so nothing can update it if restarted
Allow access to the the app and check it is all working. Depending on your app you might need to update your front end drivers
Thanks for the help, I was able to pretty easily do a test install on one of our dev machines. A couple of minor hiccups that were easily worked around (since I only migrated a single database, I had to put "use [databasename] in the top of .5gb file, but I've since found workarounds for that too). The install of both MySQL & the subsequent upgrade to MariaDB went very well. I've pointed my application toward the new database (in debug), and there are definite improvements in query speed. Our IT guy seems satisfied that even if something goes wrong we can easily get MySQL back up and running. I'm going to write a script to back up our entire MySQL database so we can do the migration to MariaDB for our production server with a fallback should something go wrong. Based on my experience this morning, I don't expect that to be a problem.
Thanks again.