Creating a DataArts Migration Incremental Package

Context

• When you create a DataArts Migration (CDM) incremental package, the system automatically creates a CDM cluster based on the specifications you select for the incremental package.
• You can locate a DataArts Studio instance, click More, and select View Packages to view your incremental packages.

a CDM Cluster

1. Locate an enabled instance and click .

2. On the displayed page, set parameters based on Table 1.

   Table 1 Parameters for the CDM incremental package

   Parameter	Description
   Package	Select DataArts Migration.
   AZ	When you your first DataArts Studio instance or incremental package, you can select any available AZ. When you create another DataArts Studio instance or incremental package, determine whether to select the same AZ as the first instance or incremental package based on your DR and network latency demands. If your application requires good DR capability, select an AZ different from that of the first instance or incremental package in the same region. If your application requires a low network latency between instances, select the same AZ as the first instance or incremental package.
   Workspace	Select the workspace where the CDM incremental package is to be used. A CDM cluster can be used in a workspace only after the CDM cluster is associated with the workspace.
   Enterprise Project	If the CDM cluster is associated with multiple workspaces, select an enterprise project for the CDM cluster.
   Cluster Name	Customize the cluster name.
   Instance Type	The following CDM cluster flavors are available: cdm.large: the large flavor with 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: the ultra-large flavor with 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: the 4x ultra-large flavor with 64 vCPUs and 128 GB of memory. The maximum and assured bandwidths are 40 Gbit/s and 36 Gbit/s. Up to 128 jobs can be executed concurrently.
   VPC	VPC, subnet, and security group to which the CDM cluster in the DataArts Studio instance belongs. If you want to connect the DataArts Studio instance or CDM cluster to a cloud service such as GaussDB(DWS), MRS, and RDS, ensure that the CDM cluster can communicate with the cloud service. If the CDM cluster and the cloud service are in the same region, VPC, subnet, and security group, they can communicate with each other by default. If the CDM cluster and the cloud service are in the same VPC but in different subnets or security groups, you must configure routing rules and security group rules. For details about the operations on VPCs, subnets, and security groups, see Virtual Private Cloud User Guide. NOTE: After the CDM cluster is created, its VPC, subnet, and security group cannot be changed. Set them carefully. You can select a VPC subnet shared by the VPC owner when you create a CDM cluster. Through VPC subnet sharing, you can easily configure and manage multiple accounts' resources at low costs. For details about how to share a VPC subnet, see .
   Subnet
   Security Group
   IPv6 Dual Stack	Whether to enable IPv6 dual stack. If you enable this function, both private IPv4 and IPv6 addresses can be used to access the cluster. NOTE: If you enable this function, you can only select subnets for which IPv6 CIDR blocks are enabled. If IPv6 CIDR blocks are disabled for the subnet you want to select, enable IPv6 CIDR blocks for the subnet in the VPC service. IPv6 dual stack can be enabled for private IP addresses, but not for public IP addresses.

   Notice

   You cannot modify the specifications of an existing cluster. If you need higher specifications, create another cluster.

3. Click Now, confirm the specifications, and click Next.
4. Go to the corresponding workspace to view the CDM cluster you have .