# Migrate MariaDB at Percona **URL:** \ **Category:** Percona Server for MySQL 8.0\ **Tags:** percona\ **Created:** [November 17, 2022, 2:51pm UTC](https://forums.percona.com/t/migrate-mariadb-at-percona/18638 "2022-11-17T14:51:14Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![alfadown](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@alfadown](https://forums.percona.com/u/alfadown)\ **Post date:** [November 17, 2022, 2:51pm UTC](https://forums.percona.com/t/migrate-mariadb-at-percona/18638/1 "2022-11-17T14:51:14Z")
My case. I have discovered this year Percona Server for MySQL. After some successful testings of this solution, I met a problem for migrating a big database of Mariadb 10.4.27 at Percona 8.0.29. I used various methods in order to migrate, but without results interesting. First method, by exporting tablespace, this method failed : ERROR 3949 (HY000): Failed to import database/table because the CFG file version (1953066341) is not compatible with the current version (5). Second method by replication : The replication seems not compatible between MariaDB 10.4 and Percona Server. Last\_SQL\_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, the server was unable to fetch a keyring key required to open an encrypted relay log file, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave. The last solution, is to make a dump with mysqldump. But this method is very very slow and need a very important downtime. Do you have a solution please? Thank you. ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [November 17, 2022, 4:26pm UTC](https://forums.percona.com/t/migrate-mariadb-at-percona/18638/2 "2022-11-17T16:26:48Z")
From here, [MariaDB versus MySQL - Compatibility - MariaDB Knowledge Base](https://mariadb.com/kb/en/mariadb-vs-mysql-compatibility/#incompatibilities-between-mariadb-104-and-mysql-80:) > MariaDB 10.2, MariaDB 10.3, and MariaDB 10.4 function as limited drop-in replacements for MySQL 5.7 You need to import tablespaces into Percona Server 5.7, not 8.0. After you have imported everything to PS 5.7, you can then upgrade from PS 5.7 to PS 8.0. > Second method by replication : Are you using GTIDs? MariaDB’s GTID is incompatible with everyone else. You need to disable GTID and use traditional binlog coordinates. ---
**Author:** ![alfadown](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@alfadown](https://forums.percona.com/u/alfadown)\ **Post date:** [November 17, 2022, 5:35pm UTC](https://forums.percona.com/t/migrate-mariadb-at-percona/18638/3 "2022-11-17T17:35:41Z")
Thank you, I think that your first solution is good. I Imagine a method of migration in two steps ( by Inplace upgrade ) . For the Second method, in the replication mode, I’m not using the GTID, but the ROW format for the binlogs. I note an other problem , the next error : 2022-11-17T16:30:48.189589Z 39 [Warning] [MY-010445] [Repl] QUERY(COMMIT or ROLLBACK) or XID\_LOG\_EVENT is not expected in an event stream outside a transaction. 2022-11-17T16:30:48.189604Z 39 [Warning] [MY-010590] [Repl] An unexpected event sequence was detected by the IO thread while queuing the event received from master ‘mysql-bin.000006’ binary log file, at position 84913620. A question for you, The Mariadb 10.4 replication is compatible with Percona 5.7 ? ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [November 18, 2022, 3:42pm UTC](https://forums.percona.com/t/migrate-mariadb-at-percona/18638/4 "2022-11-18T15:42:24Z")
It may not be. You should read over the link I provided above which lists out all the incompatibilities between MariaDB and everyone else. ---
**Author:** ![alfadown](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@alfadown](https://forums.percona.com/u/alfadown)\ **Post date:** [November 22, 2022, 10:12am UTC](https://forums.percona.com/t/migrate-mariadb-at-percona/18638/5 "2022-11-22T10:12:04Z")
@matthewb Thank you for your answers.