Scenario

CDM provides isolated clusters to ensure secure and reliable data migration. Currently, each CDM cluster supports only one server. Subsequently, CDM clusters will support automatic capacity expansion.

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 buying 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	CN North-Beijng1	Region where the CDM cluster resides. Resources in different regions cannot communicate with each other.
   AZ	AZ2	For details, see Regions and AZs.
   Name	cdm-aff1	Custom CDM cluster name
   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 20 jobs can be executed concurrently. This flavor is well suited to migrating a single database table with 10 million pieces of data or more. cdm.xlarge: 16 vCPUs and 32 GB of memory The maximum and assured bandwidths are 10 Gbit/s and 4 Gbit/s. Up to 100 jobs can be executed concurrently. This flavor is well suited to TB-level data migration requiring 10GE high-speed bandwidth. cdm.4xlarge: 64 vCPUs and 128 GB of memory The maximum and assured bandwidths are both 30 Gbit/s. Up to 300 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 more information, see the Virtual Private Cloud User Guide.
   Subnet	subnet-1
   Security Group	sg-1
   Enterprise Project	default	This parameter is available only when an enterprise project has been created on the Enterprise Project Management page. An enterprise project facilitates management of cloud resources. For more information, see the Enterprise Management User Guide.
   Auto Shutdown	No	After Auto Shutdown is enabled, if no job is running in the cluster and no scheduled job is created, a cluster will automatically shut down 15 minutes later to reduce costs. After a cluster is created, if you want to modify the configuration of auto shutdown or scheduled startup and shutdown, click the cluster name in the cluster list and click the Cluster Configuration tab. For details, see Modifying Cluster Configurations.
   Scheduled Startup	No	The CDM cluster supports scheduled startup. If this parameter is enabled, set the scheduled startup time every day.
   Scheduled Shutdown	No	During scheduled shutdown, the system does not wait for the completion of running jobs.
   Notification	No	After the function is enabled, configure a maximum of five 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.
   

   Generally, it takes 10 to 20 minutes to create a cluster. If you create a CDM cluster for the first time, it takes only one minute to create it.