All Products
Search
Document Center

Server Migration Center:Migrate VMware VMs without agents

Last Updated:Sep 08, 2023

Server Migration Center (SMC) allows you to migrate VMware VMs without agents. This way, the migration does not modify the settings of the operating system of the migration source or occupy the computing resources of the operating system in the migration source. This can effectively eliminate your concerns about server security and performance. This topic describes how to use SMC to migrate VMware VMs without agents.

Prerequisites

The preparations for the migration are complete. For more information, see Before you begin.

Background information

VMware vSphere is a virtualization platform that transforms data centers into aggregated computing infrastructures that include CPU, storage, and network resources. VMware vSphere manages these infrastructures as a unified operating environment and provides you with tools to manage the data centers that are added to the environment. The two core components of VMware vSphere are VMware ESXi and vCenter Server. VMware ESXi is a virtualization platform that is used to create and run VMs and virtual devices. vCenter Server is a service that manages multiple hosts connected on a network and pools host resources.

Open Virtualization Format (OVF) is an open standard that provides an open source, secure, effective, extensible, and portable format for packaging and distributing software for VMs. An OVF package generally consists of .ovf, .mf, .cert, .vmdk, and .iso files.

Benefits of migration without agents

  • Zero resource consumption

    The SMC client does not run inside VMs. Therefore, the migration does not consume the resources of VMs.

  • High migration efficiency

    You do not need to install an agent separately for each VM. This reduces the costs of labor and time.

  • High security

    No operations are performed within the operating system of a VM. This eliminates your concerns about security.

  • High compatibility

    The migration does not depend on the internal environment of the VM operating system. This improves the success rate of migration.

Migration process

asdad666The following content describes the process of migrating VMware VMs without agents:

  1. Create a Server Migration Connector.

    Download an OVF template for creating a Server Migration Connector in the SMC console, import the OVF template to vCenter Server, and then deploy a Server Migration Connector by using the OVF template.

  2. Import the information about the VMware VM to be migrated.

    Log on to the Server Migration Connector, configure vCenter Server and the VMware VM to be migrated, and then run commands to import the information about the VMware VM to be migrated.

  3. Create and start a migration job.

    In the SMC console, create and start a migration job as prompted. After the migration job is complete, an Elastic Compute Service (ECS) image is generated. You can create an ECS instance by using the image.

Environment requirements

The following table describes the environment requirements that vary based on the Open Virtualization Format (OVF) template.

OVF template

Configurations of a Server Migration Connector

Environment requirements for deploying a Server Migration Connector on vCenter Server

Environment requirements for deploying a Server Migration Connector on VMware ESXi

SMC VMware Connector 6.5 OVF

  • Number of vCPUs: four or more

  • Memory size: 8 GB or more

  • Disk space: 40 GB or more

  • vCenter Server version: vCenter Server 6.5, 6.7, or 7.0

  • Version of VMware ESXi on which the Server Migration Connector is deployed: VMware ESXi 6.5, 6.7, or 7.0

  • Version of VMware ESXi on which the VMware VM to be migrated is deployed: VMware ESXi 6.0, 6.5, or 6.7

  • Hardware version of the VMware VM to be migrated: VM 11, 12, 13, 14, or 15

  • VMware ESXi version: VMware ESXi 6.5 or 6.7

  • Hardware version of the VMware VM to be migrated: VM 11, 12, 13, 14, or 15

SMC VMware Connector 7.0 OVF

  • Number of vCPUs: four or more

  • Memory size: 8 GB or more

  • Disk space: 40 GB or more

  • vCenter Server version: vCenter Server 7.0

  • Version of VMware ESXi on which the Server Migration Connector is deployed: VMware ESXi 7.0

  • Version of VMware ESXi on which the VMware VM to be migrated is deployed: VMware ESXi 7.0

  • Hardware version of the VMware VM to be migrated: VM 13, 14, 15, 16, 17, 18, or 19

  • VMware ESXi version: VMware ESXi 7.0

  • Hardware version of the VMware VM to be migrated: VM 13, 14, 15, 16, 17, 18, or 19

Required account permissions for vCenter Server and VMware ESXi

  • If you deploy a Server Migration Connector on vCenter Server, the account used to log on to VMware ESXi and the account used to log on to the VMware VM to be migrated must be granted the following permissions:

    • Datastore > Browse datastore

    • Datastore > Low-level file operations

    • Host > Local operations > Create virtual machine

    • Virtual machine > Change configuration > Acquire disk lease

    • Virtual machine > Change configuration > Toggle disk change tracking

    • Virtual machine > Provisioning > Allow virtual machine download

    • Virtual machine > Provisioning > Allow disk access

    • Virtual machine > Provisioning > Allow read-only disk access

    • Virtual machine > Snapshot management > Create snapshot

    • Virtual machine > Snapshot management > Remove snapshot

  • If you deploy a Server Migration Connector on VMware ESXi, you must use an administrator account to log on to VMware ESXi.

Procedure

Step 1: Create a Server Migration Connector

SMC provides OVF templates that are used to create a Server Migration Connector. In this step, download an OVF template, import the OVF template to your vCenter Server or VMware ESXi, and then deploy a Server Migration Connector by using the OVF template.

Download and extract an OVF template

  1. Log on to the SMC console.

  2. In the left-side navigation pane, click Migration Sources.

  3. On the Migration Sources page, click Import Migration source.

  4. On the Import Migration source page, configure the parameters.

    The following table describes the parameters.

    Parameter

    Description

    Migration Source Type

    The type of the migration source. Select VMware VM from the drop-down list.

    Import Method

    The method that is used to import the information about the migration source. By default, Use Server Migration Connector to Import VMware VM is selected and cannot be changed.

    Description

    The description of the procedure for importing the information about a migration source.

  5. In the Description section, download an OVF template based on the version of your VMware ESXi or vCenter Server and decompress the downloaded package.image..png

    Note

    If no OVF template is available for the version of your VMware ESXi or vCenter Server, set the Migration Source Type parameter to Physical Machine/VM/Third-party Cloud Server. Then, use one of the following methods to import the information about the VMware VM to be migrated:

Deploy a Server Migration Connector

Import the extracted OVF template to your VMware ESXi or vCenter Server and deploy a Server Migration Connector by using the OVF template. A Server Migration Connector can be deployed on vCenter Server or VMware ESXi. You can select the deployment environment based on your business requirements.

(Recommended) Deploy a Server Migration Connector on vCenter Server

Import the OVF template of a Server Migration Connector to vCenter Server and deploy the Server Migration Connector by using the OVF template. In this example, vCenter Server 6.7 is used. To deploy a Server Migration Connector on vCenter Server, perform the following steps:

  1. Log on to vCenter Server. Find the vCenter Server host, right-click the name of the host, and then select Deploy OVF Template....adad

  2. On the Deploy OVF Template page, follow the configuration wizard to create a VM.

    1. Select an OVF template and click NEXT.

      Select Local file and click Browse... to select the extracted OVF template.ada

    2. Specify the VM name and installation location, and click NEXT.

      Enter the VM name in the Virtual machine name field and select the installation location.ada56

    3. Select a computing resource and click NEXT.daa

    4. Confirm the template information and click NEXT.adsad

    5. Select the storage and click NEXT.asdasd

    6. Select the destination network and click NEXT.adad

    7. Confirm the configurations and click FINISH.asd、

    8. After the Server Migration Connector is deployed, right-click the Server Migration Connector and choose Power > Power On.

    9. Configure the network environment to ensure that the Server Migration Connector can connect to port 443 of vCenter Server and port 902 of the ESXi host on which the VMware VM to be migrated resides. The preceding port numbers are the default port numbers.

    10. On the Summary tab, obtain the IP addresses of the Server Migration Connector.asda

Deploy a Server Migration Connector on VMware ESXi

Import the OVF template of a Server Migration Connector to VMware ESXi and deploy the Server Migration Connector by using the OVF template. In this example, VMware ESXi 7.0 is used. To deploy a Server Migration Connector on VMware ESXi, perform the following steps:

  1. Log on to VMware ESXi. In the left-side navigation pane, right-click Virtual Machines and select Create/Register VM.

    image..png
  2. In the Select creation type step, select Deploy a virtual machine from an OVF or OVA file and click Next.

    image..png
  3. In the Select OVF and VMDK files step, enter a VM name, click Click to select files or drag/drop, select the downloaded OVF template, and then click Next.

    image..png
  4. In the Select storage step, click Next.

    image..png
  5. In the Deployment options step, click Next.

    image..png
  6. In the Ready to complete step, click Finish.

    Wait until the VM is deployed. The IP address of the Server Migration Connector is displayed in the General Information section. By default, Dynamic Host Configuration Protocol (DHCP) is configured in the network settings of the Server Migration Connector. You can modify the network settings based on your business requirements.

    image..png
  7. Configure the network environment to ensure that the Server Migration Connector can connect to port 443 and port 902 of VMware ESXi. The preceding port numbers are the default port numbers.

Step 2: Import the information about the VMware VM to be migrated

Log on to the Server Migration Connector, configure the VMware VM to be migrated, and then import the information about the VMware VM to be migrated by running commands.

Configure the VMware VM to be migrated

  1. Log on to the Server Migration Connector.

    In this example, SSH remote connection is used. Perform the following steps:

    On a terminal from which the Server Migration Connector is accessible over a network, run the following command to connect to the Server Migration Connector. The default username is root, and the default password is left empty.

    ssh root@<IP address of the Server Migration Connector>
    Important

    For account security, we recommend that you change your password at the earliest opportunity.

  2. Run the following command to check whether the time on the Server Migration Connector is accurate:

    date

    If the time is inaccurate, you can run the ntpdate command to calibrate the time. In this topic, the time server at 0.asia.pool.ntp.org is used.

    ntpdate 0.asia.pool.ntp.org
    hwclock --systohc
    Warning

    If the time is inaccurate, the information about the migration source fails to be imported.

    ad
  3. Run the following commands to configure the VMware VM to be migrated on your vCenter Server or VMware ESXi:

    Note

    In this step, you can obtain all the hosts and VMs in the environment. If you already know the names of the hosts or VMs that you want to configure, skip this step and directly specify the names of the hosts or VMs. For more information, see the How do I migrate the specified VM or a VM on the specified host by performing VMware migration without agents? section of the "FAQ" topic.

    cd /root/smc
    ./configure.sh

    Configure the IP address, username, password, and port number of vCenter Server or VMware ESXi in sequence. We recommend that you use the default port 443. Sample command output:

    [root@localhost ~]# cd /root/smc
    [root@localhost smc]# ./configure.sh
    Please input vCenter/ESXi IP:192.168.XX.XX
    Please input username:administr****@vsphere.local
    Please input password:
    Please input port number(default 443):443

    The "Connect success" message is displayed, and a list of hosts is generated. Enter the ID of the host on which the VMware VM to be migrated resides. You must select a host that is in the Connected state. If an asterisk (*) is displayed in the Connected column of a host, the host is connected.

    Test to connect the vCenter/ESXi...
    Connect success!
    save to ./vmware_connect_config.json
    ========Aliyun SMC VMware Configure Tool 1.2========
    Connect success!
     Getting host list progress:
     [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>100.00%]time: 1.0s
    
    
    Host List:
    ------------------------------------------------------------------------
    ID      Name                              Version            Connected
    1       192.168.XX.XX                     6.7.0                  *
    2       192.168.XX.XX                     7.0.3                  *
    ------------------------------------------------------------------------
    Please input the ID of Host(input 0 to exit):1

    After you enter a host ID, a list of VMs is generated. Enter the ID of the VMware VM to be migrated. You must select a VM that is in the Connected state. If an asterisk (*) is displayed in the Connected column of a VM, the VM is connected.

    Test to connect 192.168.XX.XX
    Connect success!
     Getting vm list progress:
     [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>100.00%]time: 2.3s
    
    
    VM List of 192.168.XX.XX:
    ------------------------------------------------------------------------
    ID      Name                               Connected      CBT      Add
    1080    test1                                  *
    1084    win16bios                              *
    1011    centos7-bios-2                         *
    3008    centos7-uefi                           *
    2001    centos-hw10                            *
    ------------------------------------------------------------------------
    Please input the ID of VM to be migrated (input 0 to exit):1084

    Select the architecture of the VMware VM to be migrated.

    --------------------------------------------------------------
    0    x86_64
    1    i386
    2    arm64
    --------------------------------------------------------------
    Please choose the architecture:0

    Check whether the operating system recognized by the system is the actual operating system of the current VM. If the recognized operating system is incorrect, enter n, and then enter the number that corresponds to the actual operating system in the list. For example, you can enter 10 to select the Windows Server 2016 operating system.

    Note

    The preset operating system when a VM is created on vCenter Server may be incorrect. You must confirm the operating system of the VM.

    Is [CentOS 7 (64-bit)]' truly the OS of VM (y or n)?n
    ------------------------------------------------------------------------
    0  CentOS
    1  Ubuntu
    2  SUSE
    3  OpenSUSE
    4  Debian
    5  RedHat
    6  Others Linux
    7  Windows Server 2003
    8  Windows Server 2008
    9  Windows Server 2012
    10  Windows Server 2016
    11  Windows Server 2019
    12  Windows Server 2022
    ------------------------------------------------------------------------
    Please choose the OS of VM:

    Select the system disk. By default, the virtual disk with the number 10 is selected.

    --------------------------------------------------------------
    0    [datastore1] win16bios/wins16bios-000001.vmdk
    1    [datastore1] wins16bios/wins16bios_1-000001.vmdk
    --------------------------------------------------------------
    Please choose the system disk (default 0):0

    If an asterisk (*) is displayed in the Add column that corresponds to the VM name, the VM is added to the migration list.

    VM List of 192.168.XX.XX:
    --------------------------------------------------------------
    ID      Name                     Connected      CBT      Add  
    481     TEST_CLONE_1                 *      
    389     win16bios                    *                    *  
    338     hanjun_test_001              *  
    386     Aliyun_SMC_Agent_6.5         *  
    393     win16uefi   
    --------------------------------------------------------------
    Please input the ID of VM to be migrated (input 0 to exit):0
    • If you want to migrate multiple VMs, enter the IDs of the VMs to be migrated.

    • If you want to migrate only one VM, enter 0 and return to the host list. If you want to migrate VMs on other hosts, repeat the preceding steps. Otherwise, enter 0 to exit the configuration.

  4. Optional. Run the following command to view the generated vmware_connect_config.json and vmware_migrate_config.json files:

    ll

    A command output similar to the following one is returned:

    [root@localhost smc]# ll
    total 5588
    drwxrwxrwx. 4 root root     239 Oct 17 17:27 Check
    -rwxrwxrwx. 1 root root    6884 Oct 14 15:54 client_data
    -rwxrwxrwx. 1 root root     151 Oct 14 17:47 configure.sh
    drwxrwxrwx. 2 root root      72 Nov  1 01:15 dist
    -rwxrwxrwx. 1 root root   38878 Oct 14 15:54 EULA
    drwxrwxrwx. 2 root root    4096 Oct 17 17:27 Excludes
    -rwxrwxrwx. 1 root root 5633792 Oct 31 19:43 go2aliyun_client
    -rwxrwxrwx. 1 root root     146 Oct 14 15:54 user_config.json
    -rw-r--r--. 1 root root     263 Nov 10 18:05 vmware_connect_config.json
    -rw-r--r--. 1 root root   18406 Nov 10 18:07 vmware_migrate_config.json

Import the information about the VMware VM to be migrated

After you log on to the Server Migration Connector, start the SMC client and import the information about the VMware VM to be migrated to the SMC console by running commands.

Warning

When the SMC client is running, do not perform operations on the VMware VM to be migrated, such as shutting down the VMware VM, restarting the VMware VM, and creating or deleting snapshots for the VMware VM. If you create or delete snapshots for the VMware VM to be migrated, the migration may fail. If the migration fails, run the ./dist/migrate_configure command in the /root/smc home directory of the SMC client to obtain the VM configurations again. Then, run the ./go2aliyun_client --jobtype=3 command to start a new SMC client.

  1. Obtain the SMC access token or AccessKey pair.

    • Obtain the SMC access token: recommended. An SMC access token consists of an access token ID and an access token code. If you do not have an SMC access token, go to the Import Migration source page in the SMC console. In the Description section, click Generate and copy the generated access token ID and access token code.

      image..png
    • Obtain the AccessKey pair: An AccessKey pair of an Alibaba Cloud account consists of an AccessKey ID and an AccessKey secret. If you have not created an AccessKey pair, create one first. For more information, see Obtain an AccessKey pair.

  2. Log on to the Server Migration Connector and run the following commands to import the information about the VMware VM:

    chmod +x ./go2aliyun_client
    ./go2aliyun_client --jobtype=3

    Enter the SMC access token or AccessKey pair as prompted. In this example, the SMC access token is used. The returned information is similar to the following content. If the Import Source Server [s-bp14zd35128xgjdbh****] Successfully message is displayed, the information about the VMware VM to be migrated is imported.

    [root@localhost smc]# ./go2aliyun_client --jobtype=3
    [2022-11-10 10:12:17] [Info]  ========= Goto Aliyun VMware Client1.2.2 =========
    [2022-11-10 10:12:17] [Info]  Load User Config...
    Please Enter Access Token Id Or Access Id: at-bp1bq6h8194dnpod****
    Please Enter Access Token Code: ******************************
    [2022-11-10 10:12:17] [Info]  Load Client Data...
    [2022-11-10 10:12:17] [Info]  Load VMware Connect Config...
    [2022-11-10 10:12:17] [Info]  Load VMware Migrate Config...
    OS Info: Microsoft Windows Server 2016 (64-bit)
    CPU Info: Intel(R) Xeon(R) Platinum 8269CY CPU @ 2.50GHz
    CPU: 4 Cores Memory: 8.00GB
    Hostname: WIN-5KSIG3H94RM IP Address:  Mac Address: 00:50:56:b6:**:**
    [2022-11-10 10:12:17] [Info]  Verify User Account...
    [2022-11-10 10:12:17] [Info]  Generate SSH Key...
    [2022-11-10 10:12:18] [Info]  Import Source Server...
    [2022-11-10 10:12:18] [Info]  Import Source Server [s-bp131kz499d1e22f****] Successfully!
    [2022-11-10 10:12:18] [Info]  =========   Run In BackGround Daemon Mode   =========
    [2022-11-10 10:12:18] [Info]  Goto Aliyun Begin...
    [2022-11-10 10:12:18] [Info]  Check Source Server Status...
    [2022-11-10 10:12:18] [Info]  Check Replication Job Status...
    Please Goto SMC Console To Create New Job, time: 4m30s    \

Step 3: Create and start a migration job

In the SMC console, create and start a migration job as prompted. After the migration job is complete, an ECS image is generated. You can create an ECS instance by using the image.

  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 job, make sure that the migration source is in the Active state.

    image..png
  4. In the Create Migration Job dialog box, configure the parameters.

    The following table describes the parameters.

    Parameter

    Description

    Migration Job Type

    The type of the migration job. By default, VMware Agentless Migration is selected.

    Migration Job Name

    The name of the migration job.

    Note

    The job name must be unique within an Alibaba Cloud region.

    Job Description

    The description of the migration job.

    Destination Region

    The Alibaba Cloud region to which you want to migrate the VMware VM. This parameter is required. For more information about regions, see Regions and Zones.

    Destination Type

    The type of the migration destination. By default, ECS Image is selected. You can migrate the source server to an ECS image and create an ECS instance by using the image.

    Image Name

    The name of the ECS image that is generated by SMC for the VMware VM to be migrated.

    Note

    The image name must be unique within an Alibaba Cloud region.

    Destination Disk Size (GiB)

    The disk configurations of the destination server. Configure the following parameters based on your business requirements:

    • 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 "FAQ" topic.

    Expert Mode

    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 set this parameter to 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 business 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 the migration jobs involved. 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 up to 10 VPCs in a region, including the VPCs that are manually created and the VPCs that are automatically created by SMC. Therefore, you can migrate up to 10 migration sources at a time if you do not specify a VPC or a vSwitch. To increase 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, or Smart Access Gateway to connect a migration source to a VPC. For more information, see Connect a data center to a VPC.

    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 business 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.

    Checksum Verification

    Specifies whether to enable 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.

    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 FAQ.

    • BYOL: SMC allows you to bring your own license (BYOL). You can use your own Microsoft or Red Hat license to migrate a VMware VM to Alibaba Cloud. For more information, see FAQ.

    Intermediate Instance Type

    The type of the intermediate instance. Select an intermediate instance type based on your business 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, you cannot create the migration job.

    • If you do not specify an instance type, SMC automatically selects an instance type to create an intermediate instance.

    Automatic Incremental Synchronization

    Specifies whether SMC automatically synchronizes incremental data from the migration source to Alibaba Cloud.

    • To enable this feature, you must configure the following parameters:

      • Synchronization Interval: the interval at which SMC automatically synchronizes incremental data to Alibaba Cloud.

      • Maximum 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.

    Image Check

    Specifies whether to enable the image check feature. The image check feature checks whether an image is valid and whether the image can be used to create full-featured ECS instances. You can use the image check feature when you migrate servers or VMware VMs without agents.

    The image check feature helps you identify potential issues that exist in the destination images or ECS instances after migration is complete, and provides solutions to the identified issues. This improves the success rate of starting an ECS instance.

    For more information, see Configure image check.

    Execution Method

    The method that is used to run the migration job. Valid values:

    • Run Now: The migration job starts immediately after it is created.

    • Run Later: The migration job automatically starts at the specified time after it is created.

      Important

      The earliest time that you can specify to run a migration job is 10 minutes after it is created.

    • Create Only: After the migration job is created, you must manually start the job.

    Default value: Run Now.

    Migration Job Tags

    The tags that you want to specify for the migration job. Each tag contains a key and a value. You can use tags to query and manage migration jobs.

    Important

    You can specify up to 20 tags for a migration job.

  5. Click Create.

  6. On the Migration Jobs page, click the VMware Agentless Migration tab. Wait until the migration job is complete.image..png

    • If the state of the migration job changes to Completed, the migration job is successful. You can click Create Instance in the Actions column of the migration job 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 job changes to InError, the migration job fails. You can check the logs to troubleshoot the failure. Then, restart the migration job. For more information about common errors and solutions, see FAQ and Troubleshoot server migration failures.

  7. Optional. Migrate another VMware VM.

    If you specify multiple VM IDs when you configure the VMware VM to be migrated, you can close 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: To migrate another VMware VM, perform the following steps:

    1. Log on to the Server Migration Connector. For more information, see the Configure the VMware VM to be migrated section in Step 2 of this topic.

    2. Press Ctrl+C to exit the current SMC client process that is running. Then, run the following command to close 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

Step 4: (Optional) Configure multiple jobs to migrate VMs

If you want to migrate a large number of VMware VMs, you can configure multiple jobs to migrate VMs at a time to improve migration efficiency.

Important

You can close the SMC client process for a VMware VM and migrate another VMware VM only after the first VMware VM is migrated. If you close the SMC client process for a VMware VM whose migration is in progress, the VMware VM fails to be migrated.

  1. Optional. Create multiple Server Migration Connectors.

    You can run up to five SMC clients on each Server Migration Connector. If you require more than five SMC clients, you can deploy multiple Server Migration Connectors by cloning a Server Migration Connector or using the OVF template based on the remaining available resources in the current VMware environment. Then, run the SMC clients on different Server Migration Connectors. In this example, a Server Migration Connector is cloned.

    1. Right-click the Server Migration Connector to be cloned and choose Clone > Clone to Virtual Machine.asdas56

    2. Specify the VM name, installation location, computing resources, storage space, and clone options in sequence.

      For more information, see the Step 1: Create a Server Migration Connector section of this topic.

  2. Log on to the Server Migration Connector. For more information, see the Configure the VMware VM to be migrated section in Step 2 of this topic.

  3. Run the following commands to obtain multiple SMC clients for each Server Migration Connector.

    You can run up to five SMC clients on each Server Migration Connector at a time. You can copy multiple SMC client files based on your business requirements.

    cd /root
    cp -r smc smc2
    cp -r smc smc3
    cp -r smc smc4
    cp -r smc smc5
    mv smc smc1                 
    Important

    You can run up to five SMC clients on each Server Migration Connector at a time.

  4. Run the following commands to run the configuration script for each Server Migration Connector.

    If you run multiple SMC clients on a Server Migration Connector, you can go to the directory of the specified SMC client and run the ./configure.sh command to run the configuration script for the specified SMC client. In this example, the second SMC client is used.

    cd /root/smc2
    ./configure.sh

    For more information about how to run the configuration script, see the Configure the VMware VM to be migrated section in Step 2 of this topic.

  5. Run the following command to view the processes of the SMC clients that are running:

    ps -ef | grep smcvmware_client

    The following figure shows a similar command output.asda56

    Note

    When multiple SMC clients are running, the SMC client processes are named based on the time sequence in which they start, such as smcvmware_client_1, smcvmware_client_2, ..., and smcvmware_client_N.

  6. After the migration job that corresponds to each SMC client is complete, exit the SMC client process by pressing Ctrl+C. Then, run the following command to close the current SMC client process:

    ./dist/finish N

    In the command, N indicates the process sequence and must be replaced with the actual value, such as 1 or 2.

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

    ./go2aliyun_client --jobtype=3