Moving your databases to Vultr is a simple task with our managed migration system. You can migrate any existing MySQL database to a Vultr managed database, as long as the database you are migrating is publicly accessible over the internet. Vultr's database migration process uses live replication if your database meets all the requirements, or it falls back to offline backup and restore with
mysqldump if live replication isn't possible.
Vultr can do live replication of any source MySQL database if it meets the following requirements:
gtid_modemust be ON
server_idon the source, and the target does not overlap
Vultr's MySQL managed databases meet all these requirements, and it's possible to use live replication to migrate a Vultr managed database cluster to a new Vultr location.
Live replication performs a one-way sync from your source database to the target. After the initial synchronization, the replication process continues to monitor the source and replays any changes to the target until you manually stop the replication. While replication is in progress, you should treat the target cluster as a read-only copy.
If your source database doesn't meet the requirements for live replication, migration will fall back to offline backup and restore with
mysqldump. This is a one-time backup and restore; you should ensure the source database is consistent before you begin.
The migration process runs these steps:
Complete the following important information.
Make sure your target database cluster is large enough to accept the migrated data. See the screenshot below for reference:
Click Test Connection.
If successful, you'll see a message confirming that migration is ready, and which type will be performed, either
mysqldump. For example, you may see a message like this:
Connection successful! Ready to migrate via replication method.
If the test succeeds, click the Begin Migration button to proceed.
You should detach replication when you are ready to finish the migration.
Replication means that the database migration is ongoing, and any new data in the source database will continue to be copied to the target database until you detach the replication. Replication is one-way: data is replicated from the source to the target. You should not add or update data in the target until after you detach the live replication.