This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
What is an online migration?
An in-place major version migration that keeps the database online.
A server-to-server data migration that keeps the application online.
A server-to-server migration using an online connection.
You’re migrating a MySQL database running on a VM to an Azure Database for MySQL flexible server. The application can tolerate about an hour, but not several hours, of downtime. A full backup (several years of data) takes about 4 hours to restore. What’s the best option?
An online migration.
An offline migration using a full snapshot.
An offline migration using a full snapshot and an incremental snapshot.
You want to migrate your on-premises MySQL database to Azure because it exhausts processing and storage resources regularly. Near-zero downtime is preferable. Which of these approaches should you consider?
Restore the database from a snapshot and use the binary log to synchronize changes that occurred since the snapshot was taken.
Use mydumper and myloader to create and restore data.
Use Azure Database Migration Service to automate migration and minimize downtime.
You want to test application changes against realistic data. Which option should you pick?
Restore database backups into development environments.
Use a tool like mysqldump to create controlled test scenarios.
Use Azure Database for MySQL Import CLI to create test data.
You want to migrate a high-availability flexible server from one region to another. Some downtime is acceptable. Which is the simplest solution?
Use mydumper and myloader to migrate two parallel instances, then enable replication.
Use MySQL Workbench to set up two target databases and perform a migration, then enable replication.
Use Percona XtraBackup and Azure Database for MySQL Import CLI to create the target server, and then enable HA.
You must answer all questions before checking your work.
Was this page helpful?