How to Migrate Google Cloud SQL for MySQL to Vultr Managed Databases for MySQL

Vultr Managed Databases for MySQL is a high-performance, fully managed database solution offering scalability, reliability, and ease of use for your applications. With automatic backups, enhanced security features, and seamless scalability, Vultr ensures your database performs at its best while minimizing the management overhead. You can migrate an existing Google Cloud SQL for MySQL instance to a Vultr Managed Databases for MySQL cluster to transfer specific databases and cut over applications with new performance improvements.

Follow this guide to migrate from Google Cloud SQL for MySQL to Vultr Managed Databases for MySQL. You will set up a migration environment, transfer your data, and verify the integrity of the migrated database with minimal downtime for any linked applications.

Prerequisites

Before you begin, you need to:

• Have access to an existing Google Cloud SQL for MySQL instance.
• Configure your source Google Cloud SQL for MySQL Database to accept connections from all sources (0.0.0.0/0).
• Back up your source Google Cloud SQL for MySQL database to ensure a recovery option is available.
• Provision a Vultr Managed Databases for MySQL cluster with the same MySQL version, and a similar or higher size as your source Cloud SQL for MySQL database.
• Install MySQL Workbench or the mysql client tool on your workstation.

Migrate Google Cloud SQL for MySQL to Vultr Managed Databases for MySQL

You can migrate your databases from your Google Cloud SQL instance to Vultr Managed Dabatabase for MySQL cluster using two methods, live replication or backup and restore. Follow the step below to migrate your Cloud SQL for MySQL instance to a Vultr Managed Databases for MySQL cluster.

1. Log in to the Vultr Console.

2. Click Products and select Databases.

3. Click your target Vultr Managed Databases for MySQL to open its management page.

4. Verify the access credentials within the Connection Details section to use when migrating to the Vultr Managed Databases for MySQL cluster.

   

   Note

   This guide uses the example_db database with a users table that contains multiple records to test the migration process. Replace the values with your actual database and table names.

Test the Vultr Managed Databases for MySQL

Follow the steps below to test your Vultr Managed Databases for MySQL cluster and verify that the migration from your source Cloud SQL for MySQL instance is successful.

1. Log in to the Vultr Managed Databases for MySQL cluster. Replace vultr-prod.vultrdb.com, 18140 and vultradmin with your actual details.

   CONSOLE

   Copy

   $ mysql --host=vultr-prod.vultrdb.com --port=18140 --user=vultradmin --password

   Explain Code

   Powered by Vultr AgentBeta

2. List all available databases and verify that your source databases are migrated.

   SQL

   Copy

   mysql> SHOW DATABASES;

   Explain Code

   Powered by Vultr AgentBeta

   Your output should be similar to the one below.

   +--------------------+
   | Database           |
   +--------------------+
   | defaultdb          |
   | information_schema |
   | mysql              |
   | performance_schema |
   | example_db         |
   | sys                |
   +--------------------+
   6 rows in set (0.03 sec)

3. Switch to a migrated database such as example_db.

   SQL

   Copy

   mysql> USE example_db;

   Explain Code

   Powered by Vultr AgentBeta

4. List all tables in the database and verify that the records match with your source database.

   SQL

   Copy

   mysql> SHOW TABLES;

   Explain Code

   Powered by Vultr AgentBeta

   Your output should be similar to the one below.

   +----------------------+
   | Tables_in_example_db |
   +----------------------+
   | users                |
   +----------------------+
   1 row in set (0.01 sec)

5. List all rows in the users table and verify that they match with your source table.

   SQL

   Copy

   mysql> SELECT * FROM users;

   Explain Code

   Powered by Vultr AgentBeta

   Your output should be similar to the one below.

   +----+---------+---------------------+
   | id | name    | email               |
   +----+---------+---------------------+
   |  1 | Alice   | alice@example.com   |
   |  2 | Bob     | bob@example.com     |
   |  3 | Charlie | charlie@example.com |
   |  4 | Santa   | santa@example.com   |
   |  5 | Sophie  | sophie@example.com  |
   +----+---------+---------------------+
   5 rows in set (0.00 sec)

Cutover Applications to Vultr Managed Databases for MySQL

Follow the recommendations below to cutover applications to your Vultr Managed Databases for MySQL when the migration is successful.

1. Update your application's configurations with your Vultr Managed Database for MySQL cluster's credentials. For example, follow the steps below to cutover WordPress applications to the Vultr Managed Databases for MySQL.

   • Navigate to the WordPress installation directory.

     CONSOLE

     Copy

     $ cd /path/to/wordpress/directory/

     Explain Code

     Powered by Vultr AgentBeta

   • Create a backup of the configuration file to ensure safe rollback in case of any issues.

     CONSOLE

     Copy

     $ sudo cp wp-config.php wp-config.ORIG

     Explain Code

     Powered by Vultr AgentBeta

   • Open the configuration file using a text editor such as nano.

     CONSOLE

     Copy

     $ sudo nano wp-config.php

     Explain Code

     Powered by Vultr AgentBeta

   • Update database credentials. Locate the following section and replace the values with your Vultr Managed Databases for MySQL credentials.

     PHP

     Copy

     /** The name of the database for WordPress */
     define('DB_NAME', '<example-wordpress-db>');
     
     /** MySQL database username */
     define('DB_USER', '<example-user>');
     
     /** MySQL database password */
     define('DB_PASSWORD', '<example-password>');
     
     /** MySQL hostname */
     define( 'DB_HOST', '<vultr-database-host>');
     
     /** MySQL port */
     define( 'DB_PORT', '<vultr-database-port>');

     Explain Code

     Powered by Vultr AgentBeta

     Replace the following:

     • <example-wordpress-db> with the database name in your Vultr Managed Databases cluster.
     • <example-user> with the appropriate database username.
     • <example-password> with the password of your database user.
     • <vultr-database-host> with the host of your Vultr Managed Databases for MySQL cluster.
     • <vultr-database-port> with the Vultr Managed Databases for MySQL cluster port.

     Save and close the file.

   • Restart the web server to apply the configuration changes. The command may vary depending on the web server and Linux distribution you are using.

     For Apache:

     • On Debian-based systems (Ubuntu, Debian):

       CONSOLE

       Copy

       $ sudo systemctl restart apache2

       Explain Code

       Powered by Vultr AgentBeta

     • On RHEL-based systems (CentOS, Rocky Linux, AlmaLinux):

       CONSOLE

       Copy

       $ sudo systemctl restart httpd

       Explain Code

       Powered by Vultr AgentBeta

     For Nginx:

     • On all major distributions:

       CONSOLE

       Copy

       $ sudo systemctl restart nginx

       Explain Code

       Powered by Vultr AgentBeta

     If your system uses an alternative init system, such as SysVinit or OpenRC, use the appropriate restart command. Refer to your distribution’s documentation for details.

2. Delete the source Google Cloud SQL for MySQL instance after verifying that the migration is successful.

Conclusion

You have migrated from Google Cloud SQL for MySQL to Vultr Managed Databases for MySQL using back up and restore methods with mysqldump and MySQL Workbench. You exported your database from the Google Cloud SQL instance, imported it to the Vultr Managed Database for MySQL cluster, and verified the data integrity by retrieving and checking data. This process ensures that your applications run with minimal downtime as a result of the migration. Visit the Vultr Managed Databases for MySQL documentation for more information.