Move a running Data Transmission Service (DTS) instance between a dedicated cluster and a shared cluster to adjust resource allocation and billing without recreating the instance.
Prerequisites
Before you begin, make sure that:
-
A DTS dedicated cluster exists
-
The DTS instance to move is in the Running state
-
For data migration and data synchronization instances: the source database, destination database, and the dedicated cluster are all in the same region
Constraints
| Constraint | Details |
|---|---|
| DDL operations | Do not perform DDL operations on the source database while the move is in progress. DDL during the move can cause the instance to fail or leave data in an inconsistent state. |
| Region alignment | The DTS instance and its source and destination databases must reside in the same region as the dedicated cluster. |
| DU capacity (shared to dedicated only) | The dedicated cluster must have enough available DTS units (DUs). If available DUs are insufficient, the move fails. Use the class mapping table to estimate the DUs required before starting. |
| On-premises or third-party databases | If the source or destination database is an on-premises database or a database on a third-party cloud platform, add the CIDR blocks of DTS servers to the database IP allowlist before starting. See Add the CIDR blocks of DTS servers. |
Billing changes
| Move direction | Billing effect |
|---|---|
| Shared cluster to dedicated cluster | Billing stops after the move completes. For subscription instances, the billing method changes to pay-as-you-go and a refund is issued automatically. |
| Dedicated cluster to shared cluster | The instance is billed. See Billing overview. |
Move an instance
-
Go to the Dedicated Cluster page.
-
In the top navigation bar, select the region where your dedicated cluster resides from the drop-down list to the right of Workbench.
-
On the Cluster Task page, open the Task Migration panel using one of the following methods:
-
Find the dedicated cluster and choose
> Task Migration in the Actions column. -
Find the dedicated cluster, click its ID or click Details in the Actions column, and then click Task Migration at the top of the Cluster Management page.
-
-
In the Task Migration panel, configure the following parameters:
Parameter Description Supported scenarios Select the move direction: Migrate a DTS instance from a dedicated cluster to a shared cluster or Migrate a DTS instance from a shared cluster to a dedicated cluster. Type The instance type. Valid values: Data Migration, Change Tracking, Data Synchronization. Select instance The DTS instance to move. -
Click OK.
After the move
-
On the Cluster Task page, verify that the instance status is Running.
-
If you moved the instance from a shared cluster to a dedicated cluster, confirm that the billing method has changed to pay-as-you-go.
DTS instance class mapping
Use this table to estimate the DUs required before moving an instance from a shared cluster to a dedicated cluster. If the dedicated cluster does not have enough available DUs, the move fails.
| Dedicated cluster | Shared cluster |
|---|---|
| 1 DU | micro |
| 2 DU | small |
| 3 DU | medium |
| 4 DU | large |
| 5 DU | xlarge |
| 6 DU | 2xlarge |
If a data migration instance uses more than 6 DUs, it maps to the 2xlarge class in the shared cluster by default. If a data synchronization instance uses more than 4 DUs, it maps to the large class by default.