Help Center> Cloud Data Migration> User Guide> Managing Clusters> Creating a CDM Cluster
Updated on 2022-09-22 GMT+08:00
View PDF

Creating a CDM Cluster

Scenario

CDM provides isolated clusters to ensure secure and reliable data migration. Currently, a cluster supports only one server.

Prerequisites

You have applied for a VPC, subnet, and security group. If the CDM cluster tries to connect to another cloud service, ensure that the cluster and the cloud service are in the same VPC. Otherwise, an EIP is required.

If VPC peering connection is configured, the peer VPC subnet may overlap with the CDM management network. As a result, data sources in the peer VPC cannot be accessed. You are advised to use the public network for cross-VPC data migration, or contact the administrator to add specific routes to the VPC peering connection in the CDM background.

Procedure

  1. Log in to the CDM management console.
  2. Click Buy CDM Cluster. The page for a CDM cluster is displayed.
  3. Configure the cluster parameters. Table 1 describes the required parameters.

    Table 1 Parameter description

    Parameter

    Example Value

    Description

    Region

    EU-Dublin

    Region where the CDM cluster resides. Resources in different regions cannot communicate with each other.

    AZ

    AZ2

    For details, see AZs.

    Name

    cdm-aff1

    Custom CDM cluster name

    NOTE:

    After a CDM cluster is created, its name cannot be changed.

    Instance Type

    cdm.large

    Currently, the following flavors are available:

    • cdm.large: 8 vCPUs and 16 GB of memory. The maximum and assured bandwidths are 3 Gbit/s and 0.8 Gbit/s. Up to 16 jobs can be executed concurrently.
    • cdm.xlarge: 16 vCPUs and 32 GB of memory. The maximum and assured bandwidths are 10 Gbit/s and 4 Gbit/s. Up to 32 jobs can be executed concurrently. This flavor is suitable for migrating terabytes of data that requires a bandwidth of 10GE.
    • cdm.4xlarge: 64 vCPUs and 128 GB of memory. The maximum and assured bandwidths are 40 Gbit/s and 36 Gbit/s. Up to 64 jobs can be executed concurrently.

    VPC

    vpc1

    VPC, subnet, and security group where the CDM cluster belongs to, which are used to communicate with the desired data source. They can be selected based on the migration source and destination.

    • If the CDM cluster and the data source to be connected belong to different VPCs or the data source is an on-premises one, the CDM cluster needs to be bound with an elastic IP address (EIP).
    • If the data source is a cloud service, you are advised to configure the network of the CDM cluster to be the same as that of the cloud service and the CDM cluster does not need to be bound with an EIP.
    • If the data source is a cloud service, and CDM and the cloud service are in the same VPC but in different subnets, configure security group rules to interconnect the CDM cluster with the cloud service.

    For details, see the Virtual Private Cloud User Guide.

    Subnet

    subnet-1

    Security Group

    sg-1

    Enterprise Project

    default

    On the management console, click Enterprise in the upper right corner to access the enterprise project management page to create an enterprise project.

    Tags

    cluster_owner:cdm

    Tag parameters can be configured when Advanced Configuration is set to Custom.

    If you want to use the same tag to identify multiple types of cloud resources, you can customize the tag key and tag value. Then, you can filter cloud resources with the same tag in the TMS tag system.

    NOTE:
    • A cluster can have a maximum of 10 tags.
    • A tag key and a tag value can contain a maximum of 36 and 43 characters, respectively.

    Notification

    No

    After the function is enabled, configure a maximum of 20 mobile numbers or email addresses. You will be notified of job failures (only table/file migration jobs) and EIP exceptions by SMS message or email.

    NOTE:

    The EIP exception notification takes effect only after the VPC policy agency of the corresponding region is created on the IAM management console. You can also choose Authorize EIP Check > Create Agency on the Cluster Management page to create an agency.

  4. Check the current configuration and click Buy Now to go to the page for confirming the order.

    You cannot modify the flavor of an existing cluster. If you require a higher flavor, create a cluster with your desired flavor.

  5. Click Submit. The system starts to create a CDM cluster. You can view the creation progress on the Cluster Management page.
Parent topic: Managing Clusters