Migrate a DTS instance between a dedicated cluster and a public cluster

更新时间:
复制 MD 格式

You can migrate a Data Transmission Service (DTS) instance between a dedicated cluster and a public cluster.

Prerequisites

  • A DTS dedicated cluster and the DTS instance to be migrated are created.

    Note

    If the DTS instance is a data synchronization or migration instance, the source and destination databases must reside in the same region.

  • The instance must be in the Running state.

Usage notes

  • Do not perform DDL operations on the source database during the migration of a DTS instance. Otherwise, the DTS instance fails to be migrated or the data is inconsistent after the migration.

  • The DTS instance to be migrated, including the source and destination databases of the instance, must be in the region in which the DTS dedicated cluster resides.

  • After you migrate a DTS instance from a public cluster to a dedicated cluster, you are no longer charged for the DTS instance. The billing method of a subscription DTS instance is changed to pay-as-you-go and no fee is charged for the DTS instance after the DTS instance is migrated from a public cluster to a dedicated cluster. The DTS instance is automatically refunded.

  • If you migrate a DTS instance from a dedicated cluster to a public cluster, you are charged for the DTS instance. For more information, see Billing overview.

  • Before you migrate a DTS instance from a public cluster to a dedicated cluster, you must estimate the number of DTS units (DUs) required for the dedicated cluster based on the instance class of the DTS instance in the public cluster. If the available DUs of the dedicated cluster are insufficient, the migration fails. For information about the mappings between DTS instance classes in dedicated and public clusters, see the table in step 5.

Procedure

  1. Go to the DTSDTS Dedicated Clusters page.

  2. To the right of Workbench, select the region where you want to create the dedicated cluster.

    Note

    If you are logged in to the Data Management (DMS) console, select the region for the dedicated cluster to the right of Cluster Task.

  3. In the Cluster Task list, open the Task Migration panel in one of the following ways:

    • Find the target dedicated cluster and in the Operation column, click 更多设置 > Task Migration.

    • Click the name or ID of the target dedicated cluster, or click Detail in the Operation column. Then, in the upper-left corner of the Basic Information section, click Task Migration.

  4. In the Task Migration panel, configure the following parameters.

    Section

    Parameter

    Description

    Supported Scenarios

    N/A

    Select 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 based on your business requirements.

    Important

    If the source or destination database of the DTS instance is an on-premises database or a database deployed on a third-party cloud platform, you must add the CIDR blocks of DTS servers to the IP address whitelist of the database. For more information, see Add the CIDR blocks of DTS servers.

    Select the DTS instance to be migrated

    Type

    The type of the DTS instance to be migrated. Valid values:

    • Data Migration

    • Change Tracking

    • Data Synchronization

    Select instance

    The DTS instance to be migrated.

  5. Click OK.

    The following table describes the mappings between DTS instance classes in dedicated and public clusters.

    DTS instance classes in dedicated clusters

    DTS instance classes in public clusters

    1DU

    micro

    2DU

    small

    3DU

    medium

    4DU

    large

    5DU

    xlarge

    6DU

    2xlarge

    Note
    • If the number of DUs allocated to a DTS data migration instance exceeds 6, the DTS instance is converted to the 2xlarge type in a public cluster by default.

    • If the number of DUs allocated to a DTS data synchronization instance exceeds 4, the DTS instance is converted to the large type in a public cluster by default.