All Products
Search

This Product

    Server Migration Center:Migrate servers between ECS instances

    Document Center

    Server Migration Center:Migrate servers between ECS instances

    Last Updated:Jul 17, 2024

    If you need to migrate ECS instances from one account or region to another due to reasons such as insufficient resource inventory, cost optimization, disaster recovery, and instance disk scaling, you can use SMC to efficiently migrate ECS instances.

    Note

    You can also use the image copy and image share features of ECS to migrate ECS instances across accounts and within the same account. For more information, see Copy a custom image.

    Scenarios

    You can migrate servers between ECS instances in the following scenarios:

    • Scenario 1: Migrate an instance from Account A to Account B

      This scenario applies to migration between ECS instances across Alibaba Cloud accounts, in the same region, or across regions.

    • Scenario 2: Migrate data between ECS instances under the same account

      This scenario applies to the migration of ECS instances within the same Alibaba Cloud account and across regions or zones.

      • If you have not purchased an ECS instance, convert the existing source server to an ECS image, and then manually use the image to create a new ECS instance for migration.

      • If you have purchased an ECS instance and migrate the source server to the purchased ECS instance, the storage and operating system of the source server and the purchased ECS instance must be adapted.

    • Scenario 3: ECS instance disk scale-in

      Currently, ECS instances do not support system disk or data disk scale-in. If you want to scale in or out disks, you can migrate your ECS instances to a custom image or target instance with smaller disks when you migrate ECS instances across different accounts or under the same account. For more information, see Shrink a disk.

    Impacts

    Before you migrate data, you must take note of the following items, as shown in the following table.

    Item

    Description

    Migrate Data Directory

    During migration, SMC can obtain the disk partition structure of the migration source and automatically generate the destination disk partition when creating a migration task. This accelerates data transmission during the migration.

    Windows

    By default, only system disk partition C (including other directories mounted on disk C) is migrated to generate a system disk partition. If you want to migrate other partitions, such as disk D, you must select and configure the data disk when you create a migration task.

    Linux

    • If you do not enable the block replication feature, the data in all subdirectories, including shared subdirectories in the root directory, is migrated as a partition of the system disk. If you want to migrate other partitions, such as /disk1, to an independent data disk, you must select and configure the data disk when you create a migration task. For more information about how to filter or exclude files or directories that do not need to be migrated, see How do I filter or exclude files or directories that do not need to be migrated?

    • By default, if you enable the block replication feature, only the subdirectories in the root partition of the system disk, such as / and /boot, are migrated. If you want to migrate other partitions, you must select and configure the data disk when you create a migration task.

    Intermediate Instance

    Do not interfere with intermediate instances.

    To run a migration task, SMC creates a temporary intermediate instance named No_Delete_SMC_Transition_Instance within your Alibaba Cloud account. For more information, see the "How does SMC create an intermediate instance?" section of the SMC FAQ topic. During the migration, do not stop, start, restart, or release the intermediate instance. Otherwise, the migration fails. After the migration is complete, SMC automatically releases the intermediate instance.

    Note

    If you select a destination instance, the destination instance is an intermediate instance.

    IP Address

    After the migration, the IP address will change. If the service involves the configuration of the IP address, modify it after the migration.

    Underlying hardware

    After the migration, the underlying hardware of the system changes, which may invalidate the licenses of some applications bound to the hardware.

    Preparations

    • The preparations for server migration are completed. For more information, see Prepare for migration.

    • If you want to keep the public IP address unchanged and the source ECS instance uses a fixed public IP address, you can convert the public IP address to an Elastic IP Address (EIP) to retain the public IP address, disassociate the EIP from the source ECS instance, and then associate the EIP with the migrated ECS instance. For more information, see Convert the public IP address of a Virtual Private Cloud ECS instance to Elastic IP Address and Bind and unbind Elastic IP Address.

      Note

      If the source ECS instance uses an Elastic IP Address (EIP), after the migration, the source ECS instance first disbinds the EIP and then binds the EIP to the migrated ECS instance. For information about how to associate an EIP with an instance, see Associate or disassociate an EIP.

    • If you want to migrate the source ECS instance to another ECS instance, make sure that the following requirements are met:

      • You need to back up all important data in the instance to an image, snapshot, or device other than the instance.

      • The operating system of the destination ECS instance is the same as that of the source server.

      • The number of data disks attached to the destination ECS instance is greater than or equal to that of data disks attached to the source server. Otherwise, the disk data of the source server cannot be migrated to the destination ECS instance. In this case, you must attach more data disks to the ECS instance. For more information, see Attach a data disk.

      • The capacity of the system disks and data disks attached to the ECS instance is larger than or equal to that of the system disks and data disks attached to the source server. If you want to shrink the system disks and data disks attached to the source server, make sure that the capacity of the system disks and data disks attached to the destination ECS instance is larger than or equal to the size of the data on the system disks and data disks attached to the source server. Otherwise, data of the source server cannot be fully migrated to the destination ECS instance. In this case, you must scale up the data disks and system disks. For more information about how to resize a cloud disk, see Overview.

    Procedure

    Step 1: Import the information about a migration source

    Migration sources can be servers of a variety of types, such as servers in data centers, VMware VMs, and hosts on other cloud platforms. SMC supports multiple methods to import migration sources. You can select a method to import migration sources based on your business requirements. For more information, see How do I select a method to import a migration source?

    Command line one-click import migration source (recommend)

    Important

    The source server must have Internet access.

    1. Log on to the SMC console.

      Warning

      • If you want to migrate data between ECS instances that belong to different accounts, you must log on to the SMC console by using your Alibaba Cloud account.

        • If you want to import a migration source by using a command-line interface (CLI), log on to the SMC console by using the Alibaba Cloud account to which the destination ECS instance belongs.

        • If you want to use a client to import a migration source, log on to the SMC console by using the Alibaba Cloud account of the source ECS instance.

      • You must carefully distinguish the source Alibaba Cloud account from the destination Alibaba Cloud account to avoid reverse migration operations.

    2. In the left-side navigation pane, choose Migrate to Cloud > Server Migration.

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

    4. Configure the parameters as prompted and copy the activation code command. The following table describes the parameters.

      Parameter

      Description

      Migration Source Type

      The type of the migration source. Select ECS Instance.

      Import Method

      Select Use CLI to Import Server.

      Migration Source Quota

      The number of migration sources whose information you want to import by using the activation code. Valid values: 1 to 1000. Default value: 10.

      Validity period

      The validity period of the activation code. Unit: days. Valid values: 1 to 90. Default value: 30.

      Activation Code

      Generate the activation code and copy the command by performing the following steps:

      1. Click Generate.

      2. Click the Linux Shell or Windows powerShell tab based on the operating system of the source server.

      3. Click Copy to copy the activation code command.

    5. Log on to the source server, and use the administrator permissions to paste and run the copied command to import the migration source.

      Linux source server

      1. Log on to the Linux server.

      2. Use the administrator permission to paste and run the copied command to import the migration source.

        image.png

        After the command is executed, a similar Import Source Server [s-bp18x8751kgz2oyh****] Successfully! occurs A message is returned, indicating that the migration source is successfully imported.

      Windows Source Server

      1. Log on to the Windows source server.

      2. Open Windows PowerShell with administrator privileges.

      3. Run the copied command to import the information about the migration source.

        image.png

        After the command is executed, a similar Import Source Server [s-bp19rlidl3mwuptc****] Successfully! occurs A message is returned, indicating that the migration source is successfully imported.

    6. On the Server Migration page in the SMC console, view the status of the migration source in the Migration Status column.

      • If the status of the migration source is Online, the migration source is imported.

      • If the migration source is in another state, the migration source fails to be imported. See the following solutions to resolve the issue and then re-import the migration source.

        • Solve the problem by following the error message in the console or by viewing the log file in the directory of the SMC client. By default, the SMC client is installed in the following directory:

          • Windows: C:\smc

          • Linux: /smc

        • For FAQ and solutions, see SMC FAQ and Troubleshooting.

    Import the information about a migration source by using the SMC console

    Note

    • This method is not supported when you migrate ECS instances across accounts.

    • To migrate an ECS instance under the same account, you must meet the following requirements:

      • The source server (the source ECS instance) must have the Internet access capability.

      • Install the Cloud Assistant Agent on the source server. By default, ECS instances created from public images after December 1, 2017 are pre-installed with the Cloud Assistant Agent.

    • If you use a RAM user to import data to a migration source, you must grant the following permissions to the RAM user.

      • You must grant the AliyunRAMReadOnlyAccess permission to the RAM user. For more information, see Attach a custom policy to a RAM user.

      • You must grant the Cloud Assistant management permission AliyunECSAssistantFullAccess to the RAM user. For more information, see RAM RAM.

    1. Log on to the SMC console.

      Warning

      • If you want to migrate data between ECS instances that belong to different accounts, log on to the SMC console by using the Alibaba Cloud account to which the destination ECS instance belongs. For more information, see Use the Alibaba Cloud account to which the destination ECS instance belongs to log on to the SMC console.

      • You must carefully distinguish the source Alibaba Cloud account from the destination Alibaba Cloud account to avoid reverse migration operations.

    2. In the left-side navigation pane, choose Migrate to Cloud > Server Migration.

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

    4. Configure the parameters as prompted and copy the activation code command. The following table describes the parameters.

      Parameter

      Description

      Migration Source Type

      The type of the migration source. Select ECS. By default, Install SMC Client is selected.

      Data import methods

      The method that is used to import the information about the migration source. Select Import through Console.

      Region

      The region in which the source ECS instance resides.

      Instance

      The ECS instance whose information you want to import to SMC. You can select multiple ECS instances to import the information about the ECS instances at a time.

      You can enter the instance ID, instance name, private IP address, public IP address, or elastic IP address (EIP) in the search box to search for an ECS instance.

    5. After you configure the parameters, click Import.

      The import process takes about 3 to 10 minutes. Wait until the migration source is imported.

    6. On the Server Migration page in the SMC console, view the status of the migration source in the Migration Status column.

      • If the status of the migration source is Online, the migration source is imported.

      • If the migration source is in another state, the migration source fails to be imported. See the following solutions to resolve the issue and then re-import the migration source.

        • Solve the problem by following the error message in the console or by viewing the log file in the directory of the SMC client. By default, the SMC client is installed in the following directory:

          • Windows: C:\smc

          • Linux: /smc

        • For FAQ and solutions, see SMC FAQ and Troubleshooting.

    Import the information about a migration source by using the SMC client

    For more information about the SMC client, see SMC client tools.

    1. Log on to the SMC console.

      Warning

      • If you want to migrate data between ECS instances that belong to different accounts, log on to the SMC console by using the Alibaba Cloud account of the source ECS instance. For more information, see Log on to the SMC console.

      • You must carefully distinguish the source Alibaba Cloud account from the destination Alibaba Cloud account to avoid reverse migration operations.

    2. In the left-side navigation pane, choose Migrate to Cloud > Server Migration.

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

    4. In the Import Migration Source dialog box, configure the parameters. The following table describes the parameters.

      Parameter

      Description

      Migration Source Type

      The type of the migration source. Select ECS Instance.

      Data import methods

      The method that is used to import the information about the migration source. Select Use Client to Import Server.

      Description

      After Import Description, download the SMC client based on the architecture (Arm and x86) and 32-bit and 64-bit (64-bit) of the source server operating system.

    5. Import the information about the migration source.

      Perform the operations based on the operating system of the migration source.

      Important

      During the migration, do not shut down the SMC client until the migration is complete. Otherwise, the migration source is disconnected from the SMC console, and the migration fails.

      Import the information about a Windows server

      1. You can use a remote connection tool that supports file transfer. For example, you can use WinSCP to upload the SMC client package to the source Windows server.

      2. On the Windows source server, use the built-in decompression tool of Windows or the decompression tool installed by yourself to decompress the SMC client package.

      3. In the SMC client folder that corresponds to the source server, run the SMC client.

        • To run the Windows GUI version, double-click the go2aliyun_gui.exe file.

        • To run the Windows CLI version, double-click the go2aliyun_client.exe file.

        Note

        When you run the program, you must click OK to confirm that you have the administrator permissions.

      4. Obtain an activation code or AccessKey pair.

        • (recommend) Obtain activation code: In the Import Instructions section of the SMC console, click Generate activation code and copy the activation code information.

        • AccessKey pair: The AccessKey pair consists of an AccessKey ID and an AccessKey secret. If no AccessKey pair is created, create one first. For more information, see Create an AccessKey pair.

      5. Enter the activation code or AccessKey pair as prompted.

        • To run the Windows GUI version, enter the activation code or AccessKey pair in the Token Id/AK and Token Code/SK fields and click Start. For more information, see SMC client tools.

        • Command line version: Enter the activation code access_access_token_id and access_token_code values and press the Enter key.

        If the information about the migration source is imported, the following message appears: Import Source Server [s-bp11npxndknsycqj****] Successfully!

      Import the information about a Linux server

      1. You can use a remote connection tool that supports file transfer. For example, you can use WinSCP to upload the SMC client package to the source Linux server.

      2. Connect to the source Linux server and decompress the SMC client package.

        Linux 64-bit Generic is used in the example. Run the following command to decompress the package. If you use another version of the SMC client, replace the package name in the command with the name of your SMC client. 

        tar xf go2aliyun_client_linux_x86_64.tar.gz
        Note

        Linux ARM64 supports the g6r general-purpose instance family and the c6r compute-optimized instance family. For more information about instance types, see the "ARM-based enterprise-level computing instance families" section of the Overview of instance families topic.

      3. (Optional) If you do not need to migrate some files or directories, you can exclude the files or directories from being migrated. For more information, see the How do I exclude files or directories from a migration job? section of the "FAQ" topic.

        Important

        If you enable the block replication feature, you cannot exclude files or directories from the migration job.

      4. Obtain an activation code or AccessKey pair.

        • (recommend) Obtain activation code: In the Import Instructions section of the SMC console, click Generate activation code and copy the activation code information.

        • AccessKey pair: The AccessKey pair consists of an AccessKey ID and an AccessKey secret. If no AccessKey pair is created, create one first. For more information, see Create an AccessKey pair.

      5. In the SMC client folder, run the following commands to run the SMC client.

        Run the following commands as a root or sudo user based on whether you have root or sudo permissions on the operating system of the source server.

        Root user
        cd go2aliyun_client_linux_x86_64
chmod +x go2aliyun_client
./go2aliyun_client
        Sudo user
        cd go2aliyun_client_linux_x86_64
sudo chmod +x go2aliyun_client
sudo ./go2aliyun_client

      6. Enter the activation code or AccessKey pair as prompted. In this example, the activation code is used, as shown in the following figure.adad

        The following messages may appear after you enter the activation code:

        • If no snapshot dependency is installed on your source ECS instance, a message appears. The following figure shows the details of the message. You can decide whether to install a snapshot dependency based on whether you need to enable the block replication feature.

          • If you enable block replication when you create a migration task, enter yes to automatically install the snapshot driver.

          • If you do not want to enable block replication when you create a migration task, enter no.

          Important

          If the snapshot dependency fails to be installed, do not enable block replication when you create a migration job. Otherwise, the migration may fail.

          123

        • The rsync tool is installed on most mainstream migration sources. If rsync is not installed on the migration source, the SMC client displays a message. Enter yes to install rsync, as shown in the following figure.安装rsync

        • If SELinux is enabled on the migration source, you are prompted to disable SELinux. Enter yes to disable SELinux. The following figure shows how to disable SELinux.关闭SELinux

        When a similar Import Source Server [s-bp11npxndknsycqj****] Successfully! appears in the echo indicates that the migration source is imported.

        Note

        If the information about the migration source fails to be imported, you can troubleshoot the issue based on the returned message. After you fix the issue, run the following commands to exit the background program and re-import the information about the migration source based on your permissions on the operating system of the migration source. For more information about frequently asked questions (FAQ) and solutions, see SMC FAQ and Troubleshooting.

        Use sudo permissions
        sudo ./go2aliyun_client --abort
sudo ./go2aliyun_client
        Run the following command as the root user:
        ./go2aliyun_client --abort
./go2aliyun_client

    6. On the Server Migration page in the SMC console, view the status of the migration source in the Migration Status column.

      • If the status of the migration source is Online, the migration source is imported.

      • If the migration source is in another state, the migration source fails to be imported. See the following solutions to resolve the issue and then re-import the migration source.

        • Solve the problem by following the error message in the console or by viewing the log file in the directory of the SMC client. By default, the SMC client is installed in the following directory:

          • Windows: C:\smc

          • Linux: /smc

        • For FAQ and solutions, see SMC FAQ and Troubleshooting.

    Step 2: Create and start a migration task

    1. Log on to the SMC console by using the Alibaba Cloud account to which the ECS instance belongs.

      Important

      If you want to migrate servers between ECS instances across Alibaba Cloud accounts, you must distinguish the Alibaba Cloud accounts that own the source and destination ECS instances.

    2. Find the migration source that you want to manage, click Create Migration Job in the Actions column.

    3. In the Create Migration Job dialog box, configure the parameters and click Create.

      1. Configure the basic parameters. The following table describes the parameters.

        Parameter

        Description

        Example

        Migration Job Name

        The name of the migration job.

        Server migration

        Job Description

        The description of the migration job.

        test

        Destination Type (required)

        You can select a destination type based on the actual migration scenario:

        ECS Image

        Convert an existing source server to an ECS image and use the image to create an ECS instance.

        If you set the Destination Type parameter to Container Image, the following parameters are displayed:

        • Destination Region: the Alibaba Cloud region to which you want to migrate the source server. This parameter is required. For more information about regions, see Regions and zones.

        • Image Name: the name of the destination Alibaba Cloud custom image generated by SMC for the migration source.

        ECS Instance

        Migrate the source server to the purchased ECS instance. The storage and operating system of the source server and the purchased ECS instance must be adapted.

        Important

        When you migrate data to the destination instance, the operating system of the destination instance is replaced first. The automatic snapshots of the system disk are cleared and cannot be restored. If you want to retain automatic snapshots for future needs or for data security considerations, you can manually cancel the release of automatic snapshots along with the disk before the migration. For more information, see Delete automatic snapshots while releasing a disk.

        If you set the Destination Type parameter to ECS Instance, the following parameters are displayed:

        • Destination Region: the Alibaba Cloud region to which you want to migrate the source server. This parameter is required. For more information about regions, see Regions and zones.

        • Destination Instance: the ECS instance that is used as the destination instance.

        ECS Image

        Migration Test

        Specifies whether to enable the migration test feature. This feature helps you understand the feasibility and risks of a migration job before the migration job starts and provides solutions to identified issues. You can also obtain information such as the amount of data to be migrated, migration speed, and total duration of the migration. This helps reduce the issues and losses that may occur during the actual migration. During the test, you are charged for pay-as-you-go resources. By default, Migration Test is turned on.

        Warning

        If you set the Destination Type parameter to ECS Instance, snapshots are created for all disks of the destination ECS instance. If the migration test is abnormal or the Execution Method parameter is set to Test Only, the disk snapshots are automatically rolled back. During the migration test, the destination ECS instance is unavailable and all data is lost. Make sure that the destination ECS instance does not have important data.

        For more information, see Configure a migration test.

        Keep the default setting.

        Execution Method

        The mode in which the migration job is run. Select an execution method based on whether Migration Test is turned on.

        If you enable migration drills

        • Drill Only: indicates that only the migration drill task is created. After the migration drill is complete, you must manually start the migration task to migrate servers.

        • Drill and Migrate: After the drill is complete, the system automatically starts the server migration task if no drill items are in the Critical state. This is the default value.

        If migration drills are not enabled

        • Migrate Now: The migration job starts immediately after it is created. This is the default value.

        • Migrate Later: The migration job automatically starts 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: Only a migration task is created. Click Start Task in the Actions column to manually start the migration task.

        Keep the default setting.

      2. Configure the disk parameters. The following table describes the parameters.

        Parameter

        Description

        Example

        Destination Disk Size (GiB)

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

        System Disk

        • System Disk: the size of the system disk of the destination instance. Unit: GiB. Valid values: 20 to 2048. The size of the destination system disk must be larger than the amount of data on the source system disk. For example, if the total size of the source system disk is 400 GiB but the size of data stored on this disk is only 100 GiB, you must set this parameter to a value greater than 100.

          Note

          The default value of this parameter is the size of the source system disk. We recommend that you retain the default value or specify a greater value.

        • Partition<N>: the size of the partition. SMC generates a partitioning scheme for the destination disk based on the partitioning scheme of the source disk. Unit: GiB. Valid values: 0 to 14. N specifies the serial number of the partition. For example, if the system disk of the source server has only one partition, Partition0 is generated.

        Data Disk

        • Data Disk <N>: the size of the data disk of the destination instance. Unit: GiB. Valid values: 20 to 32768.

          • If you select the Data Disk <N> check box, 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 total size of the source data disk is 500 GiB but the size of data stored on this disk is only 100 GiB, you must set this parameter to a value greater than 100.

        • Partition <N>: the size of the partition. SMC generates a partitioning scheme for the destination data disk based on the partitioning scheme of the source data disk. Unit: GiB. Valid values of N: 0 to 14. <N> indicates the serial number of the partition. For example, if a data disk of the migration source has only one partition, Partition 0 is generated.

        Note

        If your migration source has no data disk or no data disk is attached to the migration source, the Data Disk parameters are not displayed. 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.

        Block Replication

        SMC allows or disallows you to turn on the switch based on whether the migration source supports block-level replication for partitions.

        • If the migration source does not support block replication for partitions, you cannot turn on the switch. If SMC uses the default method to migrate the migration source at the file level, you can modify the size of each partition on the destination disk.

        • If the migration source supports block replication for partitions, the switch is turned on by default. You can migrate disk data at the partition level. The block replication feature ensures stable data transmission. The feature also ensures that the source and destination disks use the same partitioning scheme. However, you cannot modify the size of each partition on the destination disk.

        Note

        If your source server runs Windows, block replication is enabled by default. You cannot disable this feature.

        Keep the default setting.

      3. Optional. To configure parameters such as network type and automatic incremental synchronization, click Expert Mode and configure advanced parameters. The following table describes the parameters.

        Note

        We recommend that you select Intranet Transmission network type. If you use Intranet Transmission, you can obtain a faster and more stable Data Transmission Service effect than if you use the Internet. This improves migration efficiency.

        Parameter

        Description

        Example

        Network type

        Select the network used to transfer the migrated data to the intermediate instance. By default, the public network is used. 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.

        Internet transmission (default)

        SMC migrates data to the intermediate instance over the Internet. If you select Public Network, make sure that the source server can access the Internet. You can determine 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 do not specify the VPC or vSwitch, the migration task creates an intermediate instance in the VPC and vSwitch that are automatically created by the system.

        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 source server can connect to the VPC.

        Note

        If your server in a data center, your VM, or your third-party cloud server 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 (SAG) to connect a migration source to a VPC. For more information, see Connect a data center to a VPC.

        Keep the default setting.

        Transmission Speed Limit

        The maximum bandwidth for data transmission during migration. Unit: Mbit/s.

        Keep the default setting.

        Compression Ratio

        The compression ratio of the data to be migrated. Set the compression ratio based on your business requirements.

        • In an environment with limited bandwidth, using a high compression ratio can increase the data transmission speed.

        • If a high bandwidth is available, we recommend that you do not compress data. Data compression consumes CPU resources of the migration source.

        Valid values: 0 to 10. Default value: 7. A value of 0 indicates that data is not compressed.

        Keep the default setting.

        Checksum Verification

        Specifies whether to verify data integrity by using a checksum. By default, this feature is disabled. If you enable this feature, data integrity is ensured, but transmission speed may be reduced.

        Keep the default setting.

        License Type

        The license type. Valid values:

        Keep the default setting.

        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 create a server migration job or an agentless migration job for a VMware VM.

        This feature helps you identify potential issues in images or ECS instances after the migration job is complete, and provides solutions to the identified issues. This helps you improve the success rate of starting ECS instances.

        For more information, see Configure image check.

        Keep the default setting.

        Automatic Incremental Synchronization

        Specifies whether SMC automatically synchronizes incremental data of the migration source to Alibaba Cloud. By default, this feature is disabled.

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

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

          • Upper limit 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. For more information about the best practices for incremental migration, see Migrate incremental servers.

        • If you disable this feature, incremental data is not synchronized.

        Keep the default setting.

        Migration Job Tags

        The tags that you specify for the migration job. Each tag contains a key and a value. You can use tags to query and manage migration jobs. For more information, see Use tags to manage migration sources and tasks and Use tags to fine-grained permission management.

        Note

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

        Keep the default setting.

        Intermediate Instance Type

        The type of the intermediate instance. Select an intermediate instance type based on your business requirements. This parameter is available only if you set the Target Type parameter to ECS Image.

        • If you specify an instance type, SMC creates an intermediate instance of the specified type. If the specified instance type is unavailable, you cannot create the migration job.

        • If you do not specify an instance type, SMC automatically creates an intermediate instance.

        Important

        To avoid migration errors, do not stop, start, restart, or release the intermediate instance during the migration.

        Keep the default setting.

    4. In the message that appears, read the migration notes and click Got It.

    5. On the Migration Tasks page, view the real-time migration status.

      The time required to transfer data is affected by factors such as the source data size and network bandwidth. Wait until the migration task is complete.

      image

      If the migration task is in the Synchronizing state, you can perform the following operations on the migration task:

      • Edit a migration task: In the Actions column, click Edit Task to modify the transmission speed limit, compression ratio, and checksum verification parameters.

      • Pause a migration task: Click Pause Task in the Actions column to pause the migration task.

    Verify the migration results

    • If Migration Status is Completed, the migration is successful.

      • If you set Destination Type to ECS Image,

        After the migration is complete, Alibaba Cloud custom images are generated. You can also click View Report in the Migration Deliverables column to view the image detection results. For more information, see View image detection results.

        image

        Manually verify migration results (recommend)

        You can click Create Instance in the Actions column to go to the Create ECS page in the ECS console. The custom image is selected by default. For more information about how to create an ECS instance, see Create an instance from a custom image.

        Automatically verify migration results

        Note

        To use this feature, you must install the Cloud Assistant plug-in in the instance. The system version of the instance supports this feature. For more information, see Install the Cloud Assistant Agent.

        This feature uses the OOS template ACS-SMC-CreateAndVerifyInstance provided by Alibaba Cloud to automatically verify whether the image generated by the migration task can successfully create an ECS instance and start it normally.

        1. Click Verify Migration Result in the Actions column.

          image

        2. In the dialog box that appears, read the instructions on the verification process and click Verify Now.

          You can also click Customize Verification Parameters to configure the parameters.

        3. In the Verify Migration Result column, view the verification result.

          • Verified: indicates that the migration is successful. You can click Show Output Parameters to check the details.

          • Not Verified: indicates that the migration failed. You can click View Cause to view the cause of the migration task and troubleshoot the issue based on the cause.

          You can also click the ... icon in the Actions column and select View Verification Records in OOS Console to view the template history.

      • If you set Target Type to ECS Instance, click View Target Instance in the Actions column to go to the Target Instance page and view the target ECS instance.

      After the server is migrated, you need to perform the following operations to ensure the normal operation of your business:

      • Verify and verify the data to ensure the integrity and correctness of the data. For more information, see the How do I check my system after I migrate a Linux server? or How do I check my system after I migrate a Windows server? section of the "FAQ" topic.

      • The IP address will change after the migration. If the service involves the configuration of IP addresses, modify the configuration.

        • If a domain name has been bound to the source server, the public IP address of the source server will change after the migration. You must resolve the domain name to the new public IP address of the source server. For more information, see Add a website.

        • If you want to keep the private IP address unchanged, you can modify the private IP address after the migration is complete. For more information, see Modify the private IP address of an instance.

      • If a domain name has been bound to the source server and the source server uses a fixed public IP address, the public IP address will change after the migration. You must resolve the domain name to a new server IP address. For more information, see Add a website.

    • If Migration Status is Drill Exception, the migration drill fails.

      You need to view the drill report and fix the serious drill items, and then retry the migration drill. For more information, see Configure a migration test.

    • If Migration Status is Error, the migration task fails.

      In this case, you need to troubleshoot the issue and try again:

      1. In the Actions column, click Troubleshoot Errors and fix the error based on the error code and error message. For more information, see FAQ and Errors occurred during a server migration.

      2. On the Migration Tasks page, click Retry Task.

        The migration task continues at the last completed progress.

        Important

        If the intermediate instance is released, you must create another migration job. For more information, see the What do I do if I release an intermediate instance by accident? section of the "FAQ" topic.

    Clean up resources

    • Migrate images to ECS instances

      During migration, SMC creates a temporary pay-as-you-go intermediate instance named No_Delete_SMC_Transition_Instance under your Alibaba Cloud account to assist in the migration. You need to select whether manual cleanup is required based on whether the migration is successful:

      • If the migration is successful, the intermediate instance is automatically released. You do not need to manually clean it up.

      • Migration error: The intermediate instance always exists with the migration task and costs are incurred. You can choose one of the following methods to release the intermediate instance to avoid unnecessary fee deduction:

        • If you no longer want to use the migration task, choose image > Delete in the Actions column to delete the migration task.

        • Manually release the intermediate instance. For more information, see Release an instance.

    • Migrate data to the destination instance

      During migration, SMC creates a temporary pay-as-you-go intermediate disk named SMC_Temp_Disk in the destination instance to assist in the migration. You need to select whether to manually clean the intermediate disk based on whether the migration is successful:

      • Successful migration: The intermediate disk is automatically released. You do not need to manually clean it up.

      • Migration error: The intermediate disk persists with the migration task and generates fees. You can choose one of the following methods to release the intermediate disk to avoid unnecessary fee deduction:

        • If you no longer want to use the migration task, choose image > Delete in the Actions column to delete the migration task.

        • Manually release the intermediate instance. For more information, see Release a disk.

    References

    If you need to migrate incremental data multiple times, you can perform multiple incremental migrations at a custom interval after the first full migration is complete. This synchronizes the incremental data generated by the source server to Alibaba Cloud and reduces the service suspension time and delivery time of the source server. For more information, see Migrate incremental data from a source server.