Database Migration Service overview

Available in VPC

Database Migration Service allows you to migrate databases from on-premise or other cloud environments to NAVER Cloud Platform environment rapidly and safely.

Database Migration Service features

Database Migration Service provides the following features:

• Migration task automation by stage: create migration tasks to automate required tasks for migration by stage
• Endpoint management feature: can easily create and manage the source DB endpoint
• Connection test feature: conduct connection tests between source DB and target DB before migration
• Monitoring migration task history: can view migration task status and history

About Database Migration Service user guide

Database Migration Service provides services in the Korea Region. See the following table of contents and their details for best use of Database Migration Service.

• Database Migration Service overview: introduction to Database Migration Service and related useful resources
• Prerequisites for using Database Migration Service: guide to supported specifications, supported databases and pricing information to use Database Migration Service
• Database Migration Service scenarios: introduction to the overall process to use Database Migration Service
• Getting started with Database Migration Service: introduction to the overall process to use Database Migration Service
  • Request or cancel subscription: introduction to requesting and canceling subscription to Database Migration Service
• Using Database Migration Service: introduction on how to use Database Migration Service
  • Source DB and target DB access settings: introduction on how to access source DB and target DB for migration
  • Endpoint management: introduction on how to create and manage source DB endpoint
  • Migration management: introduction on how to create and manage migration tasks
  • Event: introduction on how to view migration tasks and endpoint management history
• Managing Database Migration Service permissions: introduction on how to manage Database Migration Service permissions using Sub Account
• Database Migration Service glossary: terms you must know when using Database Migration Service
• Database Migration Service release notes: update history for Database Migration Service guide

Database Migration Service-related resources

NAVER Cloud Platform provides various related resources as well as a user guide to help customers better understand Database Migration Service. If you're a developer or marketer in need of detailed information while considering adopting Database Migration Service for your company or establishing data-related policies, then please make good use of the following resources.

• Improvements in comprehension and usage methods for Database Migration Service
  • Ncloud user environmental guide: guide on VPC environments and supported features
  • Pricing introduction, characteristics, detailed features: summary of the pricing system, characteristics, detailed features of Database Migration Service
  • Latest service news: the latest news on Database Migration Service
  • Contact us: send direct inquiries in case of any unresolved questions that aren't answered by the user guide
• Database Migration Service related services user guide
  • Cloud DB for MySQL user guide: how to use Cloud DB for MySQL supported by Database Migration Service
  • Sub Account user guide: introduction on how to use Sub Account, which aids in the management of Database Migration Service's administration permissions

Check FAQs first.

You can get your questions answered quickly by referring to the answers in the FAQs before reading the user guide. If you haven't found the answer to your question in the following FAQs, then search the user guide for what you would like to know.

Q. Can I migrate even when the MySQL versions of the source DB and the target DB are different?
A. It is recommended to migrate between the same major versions but you can use Database Migration Service even when the versions of the source DB and target DB are different. For example, you can migrate from the MySQL 5.7 version to the MySQL 8.0 version. However, the MySQL version that reached EOL can cause compatibility-related error messages during migration.

Q. Communication between the source DB and target DB servers doesn't work. What should I do?
A. You need to set the connection information to connect the source DB server and the target DB server before migration. Inspect the inbound ACG policy of the source DB and the outbound ACG policy of the target DB. For more information on connection settings by migration scenario, see Source DB and Target DB connection settings.

Q. I can't access the source DB even though I tried a test connection. What should I check?
A. You should set the firewall for the source DB server (ACG) for access from the target DB. Edit ACG's inbound rules applied to the source DB server to allow the following traffic.

• Protocol: TCP
• Access source: public domain IP address allocated to target DB (<example> 101.101.220.246/32)
• Allowed port: target DB access port

Q. DB ACL check messages are displayed when I try test connection. What should I check?
A. For source DB backup and replication, you need to allow access to the target DB, backup, and replication permissions for the account created in a mysql_native_password format. For more information, see Creating source DB account and setting ACL.

Q. What DB permissions do I need to add for migration?
A. Check whether your source DB uses GTID first. For permissions items needed for migration, see Minimum permissions required for migration.

Q. Is there any setting that I need to apply to the source DB for migration?
A. Enable the binary log server_id and specify a value. Check whether the log_bin value is displayed as ON. For more information on preparations required for Source DB replication, see Preparations.

Q. How is migration processed if the target DB has the same database name as the source DB?
A. Migration can't be processed if the target DB has the same database name as the source DB. Process migration after deleting the redundant database.

Q. What character set is supported in migration?
A. utf8, utf8mb4, and euckr are all supported. In the case of different character sets, change the DB and table character set of the source DB before migration.

Q. Is a definer account that is set in the source DB created automatically during migration?
A. User accounts are not included in the migration target. Create an account used in the definer at the target DB before migration.

Q. Is there a MySQL engine that does not support migration?
A. MyISAM, BLACKHOLE, FEDERATED, and ARCHIVE engines don't support migration.

Q. The error message "Collations unsupported in target DB are included" appeared. Why am I seeing this message?
A. It is an error message that occurs if the source DB uses the MySQL 8.0 version and the target DB uses 5.7 or an earlier version. "utf8mb4_0900_ai_ci," the default collation supported by the MySQL 8.0 version, is not supported in the 5.7 version. Change collation options in the source DB, such as database, table, view, procedure, and function, before migration.

Q. Can I migrate MariaDB?
A. Migration is possible even when the source DB is MariaDB. However, the MariaDB version that reached EOL can cause compatibility-related error messages during migration. If the same error occurs continuously, change the target DB to MySQL version 5.7 to proceed with the migration or change the version of the source DB.

Q. Is there any additional checklist related to the source DB before migration?
A. You need at least 1 or more databases in the source DB for migration.

Q. I want to migrate from source DB MySQL version 5.7 and MariaDB version 10.1 or later to target DB MySQL version 8.0. What precautions should I take?
A. The sql_mode='NO_AUTO_CREATE_USER' setting, which is supported by MySQL 5.7 and MariaDB 10.1.7 and later versions as the default value, is not supported starting with MySQL 8.0. If the setting is applied to the source DB, delete it and then perform migration. If you experience this error while importing, delete the migration and then try again. Other than that, you need to check whether there is any compatibility issue between the existing application and MySQL 8.0 before switching services.

Q. All migration steps, including replication, have been completed, but the status is displayed as "migration" in the Cloud DB for MySQL console.
A. In the migration completed (= replication completed) stage, DB service migration is finally available only when the user clicks the [Complete] button in the console.

Q. Can I also perform migration for DB Config settings?
A. Migration for DB Config settings is not supported. Please set them the same as those for the source DB on the target DB such as the Character Set/Collation.

Q. Test connection takes too much time.
A. The process may take a few minutes if there is a large number of source DB schema. It is a procedure to check authorization and inspect schemas for the normal operation of migration. Please make sure not to refresh the page as the check process will be reset.

Q. Is there something I should be aware of when using the DMS service?
A. The target DB is restarted during migration and only available for data reading. Therefore, please make sure not to designate a currently operating cluster as your target DB.