- Table Routing
- Block and Allow Lists
- Binlog Event Filter
- Migration Delay Monitoring
- Usage Scenarios
- Manage the DM Cluster
- Manage Migration Tasks
- Migrate from MySQL-compatible Database
- DM Portal
This document gives an overview of configuration files of DM (Data Migration).
inventory.ini: The configuration file of deploying DM using DM-Ansible. You need to edit it based on your machine topology. For details, see Edit the
inventory.inifile to orchestrate the DM cluster.
dm-master.toml: The configuration file of running the DM-master process, including the topology information of the DM cluster and the corresponding relationship between the MySQL instance and DM-worker (must be one-to-one relationship). When you use DM-Ansible to deploy DM,
dm-master.tomlis generated automatically. Refer to DM-master Configuration File to see more details.
dm-worker.toml: The configuration file of running the DM-worker process, including the upstream MySQL instance configuration and the relay log configuration. When you use DM-Ansible to deploy DM,
dm-worker.tomlis generated automatically. Refer to DM-worker Configuration File to see more details.
When you use DM-Ansible to deploy DM, you can find the following task configuration file template in
task.yaml.exmaple: The standard configuration file of the data migration task (a specific task corresponds to a
task.yaml). For the introduction of the configuration file, see Task Configuration File.
You can perform the following steps to create a data migration task based on
- Refer to the description in the Task Configuration File and modify the configuration in
- Create your data migration task using dmctl.
This section shows description of some important concepts.
|Uniquely identifies a MySQL or MariaDB instance, or a replication group with the primary-secondary structure. The maximum length of |
|DM-worker ID||Uniquely identifies a DM-worker (by the |