Overview
In this article, you’ll learn how to migrate a database from MariaDB, a fork of MySQL, into PlanetScale. We recommend reading through the Database import documentation to learn how imports work before proceeding.Prerequisites
- A PlanetScale account
- A MariaDB server with traffic permitted from our import IP addresses
Configure MariaDB
Before you can start migrating data, there are a number of configuration options that need to be in place for the import to work properly:binlog_formatlog_binsql_mode
The steps below edit the configuration file on a self-managed server. If your MariaDB database is hosted on Amazon RDS, you cannot edit these values directly. Instead, set them through a DB parameter group, enable binary logging by turning on automated backups, and set your binlog retention period, as described in the AWS RDS migration guide. Skip the GTID parameters in that guide, since MariaDB uses its own GTID implementation and does not have a
gtid_mode setting. Then return here to configure the migration account./etc/mysql/mariadb.conf.d/50-server.cnf. Edit the configuration file and add the following values at the end of the file:
systemctl:
Configure a migration account
PlanetScale requires a user account with a specific set of permissions on the database you wish to migrate, as well as the server itself to set up the databases that track replication changes. Connect to your MariaDB server with an account that has admin privileges, then run the following script, replacing the placeholders:<SUPER_STRONG_PASSWORD>- The password for themigration_useraccount<DATABASE_NAME>- The name of the database you will import into PlanetScale
ps_import_<id> database on your server to track replication between MariaDB and PlanetScale. The last portion of the ps_import_<id> name varies per external keyspace, which is why the grant uses a wildcard. Your server must not already contain a _vt database.
If your MariaDB database is hosted on Amazon RDS, also grant access to the RDS configuration procedure so PlanetScale can read your binlog retention setting:This procedure only exists on Amazon RDS. Running the grant against a self-managed MariaDB server fails with
ERROR 1305: PROCEDURE mysql.rds_show_configuration does not exist.GRANT statements listed. If you only see one or two lines, the grants didn’t apply correctly.
For a full explanation on what each of these grants do, our article on configuring a migration account for MySQL databases details each requirement.
Importing your database
Now that your MariaDB database is configured and ready, follow the Database imports guide to complete your import. When you create the external keyspace, use the following connection settings:- Host name (
--host) - Your MariaDB server hostname or IP address - Port (
--port) - 3306 (default for MariaDB) - Database name (
--source-database) - The exact database name to import - Username (
--username) -migration_user(created in previous section) - Password (
--password) - The password you set for the migration user - SSL verification mode (
--ssl-mode) - Select based on your MariaDB SSL configuration
- Creating your PlanetScale database
- Connecting to your MariaDB database with an external keyspace
- Checking your server settings, user grants, and schema
- Starting the import with MoveTables
- Monitoring the import progress
- Switching traffic and completing the import

