Creating a Migration Cluster

Precautions

• A maximum of two migration clusters can be created in each region in an account.
• To ensure migration stability and data security, you are not allowed to log in to nodes in migration clusters. If you indeed need to log in to the nodes, contact technical support.
• If a migration cluster is idle for more than 30 days, its status will change to Discarded. The cluster will not be deleted but cannot be restored.
• You can see the details about resources contained in a migration cluster and the security group settings of all cluster nodes in Migration Cluster Resources and Settings.

Billing

You are billed at standards rates for migration clusters and additional resources used during migrations.

• Master, migration, and list nodes in migration clusters are all ECSs, and you pay for these ECSs. For details, see ECS Pay-per-Use Billing or ECS Price Calculator.
• If you migrate over the Internet, you need to pay for NAT gateways used by migration clusters. For details, see NAT Gateway Billing or NAT Gateway Price Calculator.
• If you choose to enable log collection, you need to pay Log Tank Service (LTS) for resources you consume. For details, see LTS Billing or LTS Price Calculator.

Procedure

1. Sign in to the MgC console. In the navigation pane, under Project, select an application migration project from the drop-down list.
2. In the navigation pane, choose Deploy > Migration Clusters.
3. Click Create Cluster in the upper right corner of the page.

   If this is your first time to create a migration cluster, you need to delegate MgC the required permissions. Click to view the permissions to be assigned.

   

4. Configure the parameters listed in Table 1.

   Table 1 Parameters for creating a cluster

   Area	Parameter	Configuration	Constraints
   Basic Settings	Cluster Name	Enter a name.	The cluster name must be unique in the same account.
   	Region	Select the region to provision the cluster.	The cluster must be provisioned in the target region you are migrating to.
   	Cluster Type	Select what the cluster will be used for.	Currently, only storage migration is supported.
   Node Settings	Master Node	It is used to manage migration nodes and list nodes.	A cluster can only have one master node.
   	Migration Node	Migration nodes are used for executing migration and verification tasks. The recommended specifications are 8 vCPUs and 16 GB of memory.	The node specifications cannot be modified after the cluster is created. The number of nodes must meet the following requirements: Number of migration nodes + Number of list nodes + 1 ≤ 100 Number of migration nodes + Number of list nodes + 1 ≤ Number of unused IP addresses in the subnet
   	List Node	List nodes are used for listing tasks. The recommended specifications are 8 vCPUs and 16 GB of memory.
   Network Settings	VPC	Select a VPC from the drop-down list.	-
   	Subnet	Make sure that there are enough unused IP addresses for the migration and list nodes in this cluster.	Number of unused IP addresses in the subnet ≥ Number of migration nodes + Number of list nodes + 1
   	Network Type	Internet: You need to select a public NAT gateway. If there is no gateway available, choose Buy Gateway from the drop-down list and select the gateway specifications and EIPs you want to associate with the gateway. A maximum of 20 EIPs can be selected at a time. Intranet: This option is suitable for data migration within a region. Private line: Source data is directly accessed through the private line. For details about Direct Connect, see Direct Connect.	-
   Advanced Settings	DNS Configuration (Optional)	Enter the IP address of the DNS server to update the value of nameserver in the /etc/resolv.conf file. Use commas (,) to separate multiple DNS server addresses, for example, 192.0.2.1,192.0.2.2.	A maximum of three DNS IP addresses can be specified.
   	Domain Mapping (Optional)	Add mappings between domain names and IP addresses to update the /etc/hosts file.	A maximum of 500 mappings can be added.
   -	Traffic Limiting	Allocate the maximum bandwidth to be used by the workflow during a specified period. If you do not select this option, migration traffic is not limited. If you select this option, limit the migration traffic by setting the start time, end time, and bandwidth limit. NOTICE: For example, if you set Start Time to 08:00, End Time to 12:00, and Maximum Bandwidth to 20 MB/s, the maximum migration speed is limited to 20 MB/s when the migration task is running in the period from 08:00 to 12:00. The migration speed is not limited beyond this period.	A maximum of five traffic limiting rules can be added. The time is the local standard time of the region you are migrating to.
   	Log Collection	If this option is enabled, logs generated during the migration are collected for possible troubleshooting later. If this option is disabled, logs generated during storage migrations are not collected.	-

5. Click Confirm. Then you can view the cluster in the list. For details about cluster statuses, see Cluster Statuses. If the cluster status is Creation failed, move the cursor to the status to view the failure cause. After the fault is rectified, choose More > Retry to try to create the cluster again.
6. After the migration cluster is created, perform the following operations:
   • If the cluster status is Healthy or Subhealthy, click Create Workflow in the Operation column to .
   • Click Manage in the Operation column to add or delete nodes and traffic limiting rules for the cluster. For details, see Managing a Migration Cluster.

Upgrading Plug-ins

You can upgrade the migration plugin to the latest version for a cluster by choosing More > Upgrade Plugin in the Operation column.

Deleting a Migration Cluster

If a migration cluster is no longer needed after your data migration is complete, you can delete the cluster and the associated resources.

1. In the cluster list, locate the cluster to be deleted and choose More > Delete in the Operation column.

   

2. Select whether to delete associated resources and click OK.

   

Retrying to Create a Migration Cluster

If a migration cluster fails to be created, after you rectify the fault, you can try to create the cluster again by choosing More > Retry in the Operation column.