- About DM
- What is DM?
- Basic Features
- Advanced Features
- Merge and Migrate Data from Sharded Tables
- Migrate from MySQL Databases that Use GH-ost/PT-osc
- Filter Certain Row Changes Using SQL Expressions
- DM Architecture
- Quick Start
- Cluster Upgrade
- Manage Data Source
- Manage a Data Migration Task
- Manually Handle Sharding DDL Lock
- Manage Schemas of Tables to be Migrated
- Handle Alerts
- Daily Check
- Usage Scenarios
- Performance Tuning
- Release Notes
This document gives an overview of configuration files of DM (Data Migration).
dm-master.toml: The configuration file of running the DM-master process, including the topology information and the logs of the DM-master. For more details, refer to DM-master Configuration File.
dm-worker.toml: The configuration file of running the DM-worker process, including the topology information and the logs of the DM-worker. For more details, refer to DM-worker Configuration File.
source.yaml: The configuration of the upstream database such as MySQL and MariaDB. For more details, refer to Upstream Database Configuration File.
You can take the following steps to create a data migration task:
- Load the data source configuration into the DM cluster using dmctl.
- Refer to the description in the Task Configuration Guide and create the configuration file
- Create the data migration task using dmctl.
This section shows description of some important concepts.
|Uniquely represents a MySQL or MariaDB instance, or a migration group with the primary-secondary structure. The maximum length of |
|DM-master ID||Uniquely represents a DM-master (by the |
|DM-worker ID||Uniquely represents a DM-worker (by the |
Was this page helpful?