Server Migration Center:Create an agentless migration task for a VMware VM

Procedure

1. Log on to the SMC console.
2. In the left-side navigation pane, click Migration Sources.
3. On the Migration Sources page, click the VMware VM tab, find the migration source that you want to use, and then click Create Migration Job in the Actions column.
   Important Before you create a migration task, make sure that the migration source is in the Active state.

   
4. In the Create Migration Job dialog box, set the parameters as required.
   The following table describes the parameters.

   Parameter	Description
   Migration Job Type	The type of the migration task. By default, VMware Agentless Migration is selected.
   Basic Settings
   Destination Region	Required. The Alibaba Cloud region to which you want to migrate the VMware VM. For more information about regions, see Regions and zones.
   Migration Job Name	The name of the migration task. Note The task name must be unique within an Alibaba Cloud region.
   Job Description	The description of the migration task.
   Destination Disk Size (GiB)	The disk configurations of the destination server. Set the following parameters based on your business requirements: By default, Enable Block Replication is selected and cannot be cleared. The block replication feature ensures stable data transmission. The feature also ensures that the source and destination disks use the same partitioning scheme. You cannot modify the size of each partition on the destination disk. System Disk: the system disk size of the VMware VM. Unit: GiB. Data Disk<N>: the data disk size of the destination ECS instance. Unit: GiB. Valid values: 20 to 32768. If you select Data Disk<N>, a destination data disk is generated. N indicates the serial number of the data disk. The size of the destination data disk must be larger than the amount of data on the source data disk. For example, if the size of the source data disk is 500 GiB and the size of data stored on this disk is 100 GiB, you must set this parameter to a value greater than 100. Note Data Disk<N> is displayed only if the migration source has a data disk. For more information, see the Why are the data disk parameters of a migration source not displayed in the Create Migration Job dialog box? What do I do? section of the "SMC FAQ" topic.
   Destination Type	By default, ECS Image is selected. You can migrate the source server to an ECS image and then create an ECS instance by using the image. The following section describes the parameters that you can set after you select ECS Image as Destination Type.
   Image Name	The name of the ECS image that is generated by SMC for the VMware VM to be migrated. Note The name must be unique within an Alibaba Cloud region.
   License Type	The type of the license to be used for the migration. Valid values: Alibaba Cloud: the Microsoft license provided by Alibaba Cloud. For more information, see the SMC FAQ section of the "SMC FAQ" topic. BYOL: SMC allows you to bring your own license (BYOL). You can use your own Microsoft or Red Hat license to migrate a server to Alibaba Cloud. For more information, see the SMC FAQ section of the "SMC FAQ" topic.
   Automatic Incremental Synchronization	Specifies whether SMC automatically synchronizes incremental data of the migration source to Alibaba Cloud. To enable this feature, you must set the following parameters: Synchronization Interval: the interval at which SMC automatically synchronizes incremental data to Alibaba Cloud. Upperlimit of Reserved Images: the maximum number of images that can be retained during incremental migration. SMC automatically synchronizes incremental data to Alibaba Cloud at the specified interval. You must enable the Changed Block Tracking (CBT) feature for incremental migration. For more information about the best practices for incremental migration, see Migrate incremental data from a VMware VM without an agent. If you disable this feature, incremental data is not synchronized.
   Execution Method	The method that is used to run the migration task. Valid values: Run Now: The migration task starts to run immediately after it is created. Run Later: The migration task automatically starts to run at the specified time after it is created. Note The earliest time that you can specify to run a migration task is 10 minutes after the task is created. Create Only: After the migration task is created, you must manually start the task. Default value: Run Now.
   Tags and Network (Optional)
   Migration Job Tags	The tags that you specify for the migration task. Each tag contains a key and a value. You can use tags to query and manage migration tasks. Note You can specify up to 20 tags for a migration task.
   Network Type	The type of the network that is used to migrate data to the intermediate instance. During migration, SMC creates an intermediate instance that connects to a vSwitch in a virtual private cloud (VPC). If you select Public Network, a public IP address is assigned to the intermediate instance. Valid values: Public Network: SMC migrates data to the intermediate instance over the Internet. If you select Public Network, make sure that the migration source can access the Internet. You can choose whether to specify a VPC and a vSwitch based on your requirements. If you specify a VPC and a vSwitch, SMC creates an intermediate instance that connects to the specified VPC and vSwitch. If you migrate multiple migration sources at a time, you can specify the same VPC and vSwitch for migration tasks. This improves the usage of VPC resources. In this case, you can migrate up to 100 migration sources at a time. If you do not specify a VPC or a vSwitch, SMC automatically creates a VPC and a vSwitch, and creates an intermediate instance that connects to the VPC and the vSwitch. If you do not specify a VPC or a vSwitch before you migrate multiple migration sources at a time, SMC creates a VPC for each intermediate instance. Note Each Alibaba Cloud account can have a maximum of 10 VPCs in a region, including the VPCs that you create and the VPCs that are automatically created by SMC. Therefore, you can migrate a maximum of 10 migration sources at a time if you do not specify a VPC or a vSwitch. To raise the VPC quota, submit a ticket. VPC: SMC migrates data to the intermediate instance over a VPC. If you select VPC, you must specify a VPC and a vSwitch and make sure that the migration source can connect to the VPC. Note If your server in a data center, your VM, or your cloud host can connect to a VPC, we recommend that you select this network type to migrate data. Compared with migration over the Internet, migration over a VPC is more efficient and stable. You can use VPN Gateway, Express Connect, and Smart Access Gateway to connect a migration source to a VPC. For more information, see Connect a data center to a VPC.
   Advanced Settings (Optional)
   Checksum Verification	This feature enhances the verification of data consistency between the migration source and the destination server. However, this may slow down data transmission. By default, this feature is disabled.
   Transmission Speed Limit	The maximum bandwidth for data transmission during migration. Unit: Mbit/s.
   Compression Ratio	The compression ratio of the data to be migrated. Set the compression ratio based on your requirements. If the bandwidth is limited, a high compression ratio improves the transmission efficiency. If a high bandwidth is available, we recommend that you do not compress data. Data compression consumes the CPU resources of the migration source. Valid values: 0 to 10. Default value: 7. A value of 0 indicates that data is not compressed.
   Intermediate Instance Type	The type of the intermediate instance. Select an intermediate instance type based on your requirements. If you specify an instance type, SMC creates an intermediate instance based on the specified instance type. If the specified instance type is unavailable, the migration task fails to be created. If you do not specify an instance type, SMC automatically selects an instance type to create the intermediate instance.

5. Click Create.
6. On the Migration Jobs page, click the VMware Agentless Migration tab. Wait until the migration task is complete.
   • If the state of the migration task changes to Completed, the migration is successful. You can click Create Instance in the Actions column of the migration task to create an ECS instance by using the custom image that is generated. For more information, see Create an instance by using the wizard.
   • If the state of the migration task changes to InError, the migration task fails. You can check the logs to troubleshoot the failure. Then, restart the migration task. For more information about common errors and solutions, see SMC FAQ.
7. Optional:Migrate another VMware VM.
   If you add multiple VM IDs when you import the configuration script of the migration source, you can terminate the SMC client process after the current VMware VM is migrated, and then migrate another VMware VM. To migrate another VMware VM, perform the following steps:
   1. Log on to the SMC client VM. For more information, see Substep 4 in Step 1 of this topic.
   2. Press Ctrl+C to exit the current SMC client process that is running. Then, run the following command to terminate the SMC client process:

      ./dist/finish 1

   3. Run the following command to start a new SMC client. Then, migrate another VMware VM.

      ./go2aliyun_client --jobtype=3