Creating a Migration Cluster

Procedure

1. Sign in to the MgC console. In the navigation pane, select the created application migration project from the drop-down list.
2. In the navigation pane on the left, choose Other > 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

   Region	Parameter	Configuration	Constraints
   Basic Settings	Cluster Name	Enter a custom name.	Cluster names 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 Specifications	Select the specifications of the master node. The master node is used to manage migration nodes and list nodes in the cluster. The master node is created by default. You do not need to configure it.	The master node has the same specifications as migration nodes.
   	Migration Node Specifications	Migration nodes are used for migration and verification. It is recommended that you use C-series ECSs with 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 Specifications	List nodes are used for listing files to be migrated. It is recommended that you use C-series ECSs with 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	Select Intranet.	Migrating data within a region is over the intranet. No EIP is required.
   -	Limit Traffic	Set the maximum bandwidth to be used by the migration workflow during different periods. 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 selected.
   	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 the migration 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.