How to Migrate Azure Database for MySQL to Vultr Managed Databases for MySQL

Azure Database for MySQL is a fully managed relational database service built on the MySQL Community Edition. Migrating from Azure Database for MySQL to Vultr Managed Databases for MySQL offers predictable pricing, automated backups, and seamless integration with Vultr's global infrastructure. Vultr Managed Databases for MySQL provides a cost-effective solution with a developer-friendly interface, allowing you to focus on building applications rather than managing database infrastructure.

This guide explains how to migrate your Azure Database for MySQL to Vultr Managed Databases for MySQL with minimal downtime. You will configure network access, back up your source database, transfer your data, and verify the migration before cutting over applications.

Prerequisites

Before you begin, you need to:

• Have access to an existing Azure Database for MySQL - Flexible Server.
• Provision a Vultr Managed Databases for MySQL cluster with the same MySQL version and a similar or higher size as your source Azure database.
• Install MySQL Workbench or the mysql client tool on your workstation.

Allow Network Connections to the Source Azure Database for MySQL

Azure Database for MySQL uses firewall rules to restrict access by default. Configure firewall rules to allow connections from your management workstation and the Vultr migration service.

1. Log in to the Azure Portal.

2. Navigate to Azure Database for MySQL flexible servers and select your target server.

3. In the left menu, click Networking under Settings.

4. Under Firewall rules, click Add current client IP address to allow your workstation.

5. To allow unrestricted access during migration, add a rule with:

   • Rule name: AllowAll
   • Start IP address: 0.0.0.0
   • End IP address: 255.255.255.255

6. Click Save to apply the firewall rules.

   Note

   Remove the AllowAll rule after completing the migration for security purposes.

7. Verify the connection details on the Overview page. Note the Server name (hostname) which typically follows the format YOUR-SERVER.mysql.database.azure.com.

Back Up the Source Azure Database for MySQL

Create a backup of your Azure database before migration to ensure you have a recovery option in case of errors.

1. Connect to your Azure Database for MySQL using the mysql client. Replace YOUR-SERVER with your server name and YOUR-USERNAME with your admin username.

   CONSOLE

   Copy

   $ mysql -h YOUR-SERVER.mysql.database.azure.com -u YOUR-USERNAME -p

   Explain Code

   Powered by Vultr AgentBeta

   Enter your password when prompted.

2. List all databases to identify which ones to migrate.

   SQL

   Copy

   mysql> SHOW DATABASES;

   Explain Code

   Powered by Vultr AgentBeta

   Your output should be similar to the one below:

   +--------------------+
   | Database           |
   +--------------------+
   | information_schema |
   | mysql              |
   | performance_schema |
   | sys                |
   | webapp_production  |
   | analytics_db       |
   +--------------------+
   6 rows in set (0.12 sec)

3. Exit the MySQL console.

   SQL

   Copy

   mysql> EXIT;

   Explain Code

   Powered by Vultr AgentBeta

4. Back up all databases to a single file. Replace YOUR-SERVER and YOUR-USERNAME with your Azure credentials.

   CONSOLE

   Copy

   $ mysqldump -h YOUR-SERVER.mysql.database.azure.com \
       -u YOUR-USERNAME -p --all-databases \
       --set-gtid-purged=OFF --single-transaction \
       --triggers --routines > azure_all_databases.sql

   Explain Code

   Powered by Vultr AgentBeta

   To back up a specific database:

   CONSOLE

   Copy

   $ mysqldump -h YOUR-SERVER.mysql.database.azure.com \
       -u YOUR-USERNAME -p webapp_production \
       --set-gtid-purged=OFF --single-transaction \
       --triggers --routines > webapp_production.sql

   Explain Code

   Powered by Vultr AgentBeta

   The --set-gtid-purged=OFF option prevents MySQL from including Global Transaction Identifiers in the backup, avoiding conflicts when importing to Vultr.

5. Verify the backup file exists.

   CONSOLE

   Copy

   $ ls -lh azure_all_databases.sql

   Explain Code

   Powered by Vultr AgentBeta

6. Compress the backup for faster transfer.

   CONSOLE

   Copy

   $ gzip azure_all_databases.sql

   Explain Code

   Powered by Vultr AgentBeta

Migrate Azure Database for MySQL to Vultr Managed Databases for MySQL

You can migrate your databases using live replication through the Vultr Console, MySQL Workbench, or backup restoration with mysqldump. Choose the method that best fits your requirements.

1. Log in to the Vultr Console.

2. Click Products and select Databases.

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

4. Verify the connection credentials in the Connection Details section.

   

Test the Vultr Managed Databases for MySQL

Verify that all data migrated correctly before cutting over applications.

1. Log in to your Vultr Managed Databases for MySQL cluster.

   CONSOLE

   Copy

   $ mysql -h VULTR-DATABASE-HOST -P VULTR-DATABASE-PORT -u vultradmin -p

   Explain Code

   Powered by Vultr AgentBeta

2. Check the MySQL version matches your source Azure database.

   SQL

   Copy

   mysql> SELECT @@version;

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   +-----------+
   | @@version |
   +-----------+
   | 8.0.35    |
   +-----------+
   1 row in set (0.10 sec)

3. List all databases and verify your Azure databases are present.

   SQL

   Copy

   mysql> SHOW DATABASES;

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   +--------------------+
   | Database           |
   +--------------------+
   | defaultdb          |
   | information_schema |
   | mysql              |
   | performance_schema |
   | sys                |
   | webapp_production  |
   | analytics_db       |
   +--------------------+
   7 rows in set (0.08 sec)

4. Switch to a migrated database.

   SQL

   Copy

   mysql> USE webapp_production;

   Explain Code

   Powered by Vultr AgentBeta

5. List tables and verify the schema structure.

   SQL

   Copy

   mysql> SHOW TABLES;

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   +---------------------------+
   | Tables_in_webapp_production |
   +---------------------------+
   | users                     |
   | orders                    |
   | products                  |
   +---------------------------+
   3 rows in set (0.05 sec)

6. Compare row counts with your source database.

   SQL

   Copy

   mysql> SELECT COUNT(*) FROM users;

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   +----------+
   | COUNT(*) |
   +----------+
   |    15000 |
   +----------+
   1 row in set (0.03 sec)

7. Exit the MySQL console.

   SQL

   Copy

   mysql> EXIT;

   Explain Code

   Powered by Vultr AgentBeta

Cutover to Vultr Managed Databases for MySQL

After verifying the migration, update your applications to connect to the Vultr database.

Update WordPress Applications

1. Navigate to your WordPress installation directory.

   CONSOLE

   Copy

   $ cd /path/to/wordpress/

   Explain Code

   Powered by Vultr AgentBeta

2. Back up the configuration file.

   CONSOLE

   Copy

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

   Explain Code

   Powered by Vultr AgentBeta

3. Open the configuration file.

   CONSOLE

   Copy

   $ sudo nano wp-config.php

   Explain Code

   Powered by Vultr AgentBeta

4. Update the database connection settings with your Vultr credentials.

   PHP

   Copy

   /** The name of the database for WordPress */
   define('DB_NAME', 'webapp_production');
   
   /** MySQL database username */
   define('DB_USER', 'vultradmin');
   
   /** MySQL database password */
   define('DB_PASSWORD', 'YOUR-VULTR-PASSWORD');
   
   /** MySQL hostname */
   define('DB_HOST', 'VULTR-DATABASE-HOST:VULTR-DATABASE-PORT');

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

5. Restart your web server.

   • Apache on Debian/Ubuntu:

     CONSOLE

     Copy

     $ sudo systemctl restart apache2

     Explain Code

     Powered by Vultr AgentBeta

   • Apache on RHEL/CentOS:

     CONSOLE

     Copy

     $ sudo systemctl restart httpd

     Explain Code

     Powered by Vultr AgentBeta

   • Nginx:

     CONSOLE

     Copy

     $ sudo systemctl restart nginx

     Explain Code

     Powered by Vultr AgentBeta

Update Docker Applications

1. Open your Docker Compose file.

   CONSOLE

   Copy

   $ nano docker-compose.yml

   Explain Code

   Powered by Vultr AgentBeta

2. Update the database environment variables.

   YAML

   Copy

   services:
     app:
       environment:
         MYSQL_HOST: "VULTR-DATABASE-HOST"
         MYSQL_PORT: "VULTR-DATABASE-PORT"
         MYSQL_USER: "vultradmin"
         MYSQL_PASSWORD: "YOUR-VULTR-PASSWORD"
         MYSQL_DATABASE: "webapp_production"

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

3. Restart the containers.

   CONSOLE

   Copy

   $ docker compose down
   $ docker compose up -d

   Explain Code

   Powered by Vultr AgentBeta

Conclusion

You have migrated your Azure Database for MySQL to Vultr Managed Databases for MySQL. This guide covered configuring network access, backing up your source database, transferring data using the Vultr Console, MySQL Workbench, or mysqldump, and verifying the migration. Your applications now benefit from Vultr's predictable pricing and global infrastructure. For more information on managing your Vultr Managed Databases for MySQL cluster, visit the product documentation.