The proxy group is the basic unit for executing migration tasks, enabling centralized management and scheduling of proxy nodes. This article explains the steps for creating a proxy group. ## Notes * A maximum of 20 proxy groups can be created per account in each region * Each proxy group can contain up to 10 proxies * Each proxy group can run up to 5 migration tasks concurrently ## Instructions Each proxy can connect to one DMS Agent. By creating multiple proxies within a proxy group, you can manage multiple agents in one group When you connect multiple agents through a proxy group, if all agents are on servers with identical data, these agents will read and write data in parallel to increase migration speed However, if the servers where the agents are deployed have different data, some data may fail to migrate during migration tasks. In this case, **you must configure separate proxy groups for each data source**. After you start the DMS Agent, it automatically tries to establish a connection with the data migration service After the connection is successful, the proxy status on the DMS console will change from abnormal to running, and the proxy group status will change from abnormal to normal. You can then use this proxy group to create migration tasks. ## Steps 1. Log in to the [DMS Console](https://console.volcengine.com/dms). 2. In the left navigation bar, select **DMS2.0** \> **Proxy Group Management**. 3. In the top navigation bar of the **Proxy Group Management** page, select a region. 4. Click **Create Proxy Group**. 5. In the **Create Proxy Group** dialog, configure the following parameters. |**Parameters** |**Description** | |---|---| |Name |Set the proxy group name using the following rules:

* Between 3 and 32 characters.

* Contain only lowercase letters, numbers, or hyphens (\-).

* The name cannot start or end with a hyphen (\-). | |Network type |Select the network type used for data migration as described below:

* **Public network**: Migrate data using a public network. This option requires that the server containing the data to be migrated can access the public domain name of the target storage bucket.

warning

When migrating data via a public network, the source server generates additional outgoing traffic, which may result in corresponding traffic charges.

* **Private network**: Migrate data using a private network. This option requires that the server containing the data to be migrated can access the private domain name of the target storage bucket. | 6. After configuration, click **OK**.

Data Migration Service