After you import the information of a migration source, Server Migration Center (SMC) automatically generates a record for the migration source. You must create and start a migration task for the migration source in the SMC console. This topic describes how to create and start a migration task.

Prerequisites

  • The information of the migration source is imported. For more information, see Step 1: Import the information of a migration source.
  • The migration source is in the Active state. If the migration source is not in the Active state, you cannot create a migration task for the migration source. For more information about how to restore a migration source to the Active state, see the "What can I do if I cannot create a migration task because a migration source is not in the Active state?" section in SMC FAQ.

Background information

SMC can obtain the partitioning scheme of a source disk used by the migration source and generate the same partitioning scheme for the destination disk. This also accelerate data transmission during migration.

Procedure

  1. Log on to the SMC console.
  2. Step 3: Create a migration job.
    1. In the left-side navigation pane, click Migration Sources.
    2. Find the migration source, and click Create Migration Task in the Actions column.
      You can obtain the ID of the migration source from the SMC client, as shown in the following figure. Then, you can use the ID to find the migration source in the SMC console. For more information, see Step 1: Import the information of a migration source. Obtain the ID of the migration source
    3. In the Create Migration Task panel, read the instructions and set the parameters for the migration task.

      The Basic Configuration section includes the following parameters:

      • Target Region: Required. The ID of the destination region. For more information about Alibaba Cloud regions, see Regions and zones.
      • Task name: the name of the migration task.
        Note The task name must be unique within an Alibaba Cloud region.
      • Description: the description of the migration task.
      • Target Disk Size (GiB): the disk configuration of the destination server. adad

        The following table describes the parameters.

        Parameter Required Description
        Enable Block Replication No
        • If you select Enable Block Replication, stable data transmission is ensured. The block replication feature also ensures that the source and destination disks use the same partitioning scheme. You cannot modify the size of each partition in the destination disk. After you select Enable Block Replication, the Whether to enable block replication switch appears next to Partition <N>.
        • If you clear Enable Block Replication, SMC uses the default method to migrate the migration source. You can modify the size of each partition in the destination disk.
        Note If your source server runs Windows, block replication is enabled by default. Do not disable it.
        System Disk Yes
        • System Disk: the system disk size of the destination ECS instance. Unit: GiB. Valid values: 20 to 500. The size of the destination system disk must be greater than the amount of data in the source system disk. For example, if the total size of the source system disk is 400 GiB but the size of data stored in this disk is only 100 GiB, you must set this parameter to a value greater than 100 GiB.
          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>: SMC generates a partitioning scheme for the destination system disk based on that of the source system disk. Unit: GiB. Valid values: 0 to 98. N indicates the serial number of the partition. For example, if the system disk of the migration source has only one partition, Partition 0 is generated.
        • Whether to enable block replication: This switch is available only when you select Enable Block Replication. SMC allows or disallows you to turn on the switch based on whether the migration source supports block replication.
          • If the migration source does not support block replication for partitions, you cannot turn on the switch.
          • If the migration source supports block replication for partitions, you can turn on the switch to migrate disk data at the partition level.
        Data Disk <N> No
        • Data Disk <N>: the data disk size of the destination ECS 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 greater than that of the existing data in the source data disk. For example, if the total size of the source data disk is 500 GiB but the size of data stored in the disk is only 100 GiB, you must set this parameter to a value greater than 100 GiB.
        • Partition <N>: SMC generates a partitioning scheme for the destination system disk based on that of the source system disk. Unit: GiB. Valid values: 0 to 141. 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.
        • Whether to enable block replication: This switch is available only when you select Enable Block Replication. SMC allows or disallows you to turn on the switch based on whether the migration source supports block replication.
          • If the migration source does not support block replication for partitions, you cannot turn on the switch.
          • If the migration source supports block replication for partitions, you can turn on the switch to migrate disk data at the partition level.
        Note Data Disk <N> is available only if the migration source has a data disk. For more information, see SMC FAQ.
      • Resource Type: the type of the destination image. Valid values:
        • ECS Image. The following table describes the parameters.
          Parameter Required Description
          Image Name No The name of the destination ECS image generated by SMC for the migration source.
          Note The image name must be unique within an Alibaba Cloud region.
          License Type Yes The license type.
          Automatic Incremental Synchronization No 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. For more information about best practices for incremental migration, see Migrate incremental data from a source server.
          • If you disable this feature, incremental data is not synchronized.
        • ECS Instance. The following table describes the parameters.
          Note The storage and operating systems of the source server and destination instance must be compatible. For more information, see Migrate servers to ECS instances.
          smc-instance
          Parameter Required Description
          Destination Instance Yes The destination ECS instance.
          License Type Yes The license type.
          Automatic Incremental Synchronization No 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. For more information about best practices for incremental migration, see Migrate incremental data from a source server.
          • If you disable this feature, incremental data is not synchronized.
        • Container Image. The following table describes the parameters.
          Note
          Parameter Required Description
          Namespace Yes The namespace of the destination container image.
          Repository Name Yes The name of the repository that stores the destination container image.
          Version No The version of the destination container image.
          RAM Role Yes The RAM role that is attached to the intermediate instance.
      • Method to Run: specifies whether to run the task immediately after it is created or automatically run the task.
        • Run Now: The migration task runs immediately after it is created.
        • Run Later: The migration task automatically runs 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 its creation.
        • Create Only: After the task is created, you must manually start the task.

        Default value: Run Now.

      Tag and Network (Optional):

      • Migration Task Tag: 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 a maximum of 20 tags for a migration task.
      • Network Type: the type of the network that is used to migrate data to an intermediate instance. During migration, SMC creates an intermediate instance that connects to a vSwitch in a VPC. If you select Public Network, a public IP address is assigned to the intermediate instance. adda

        The following table describes the parameters.

        Parameter Description
        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. You can migrate a maximum of 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. 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, virtual machine, or cloud host can connect to a VPC, we recommend that you select this mode 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: This feature enhances the verification of data consistency between the migration source and the destination server. However, this may reduce the rate of data transmission.

        By default, this feature is disabled.

      • Transmission Speed Limit: the maximum bandwidth for data transmission during migration. Unit: Mbit/s.
      • Compression Level: the compression ratio of 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 CPU resources of the migration source.

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

      • Intermediate Instance Type: The type of the intermediate instance. Select an intermediate instance type based on your needs. The parameter takes effect only when Resource Type is set to ECS Image or Container Image.
        • If you specify the parameter, SMC creates an intermediate instance based on the specified instance type. If the specified instance type is unavailable, you cannot create the migration task.
        • If you do not specify the parameter, SMC automatically creates an intermediate instance.
    4. After the configuration is complete, click OK.
  3. Start the migration task.
    Note If you set the Method to Run parameter to Run Now, skip this step. If you set the Method to Run parameter to Create Only or Run Later, you can perform the following steps to start the migration task:
    1. In the left-side navigation pane, click Migration Tasks.
    2. Find the migration task and click Start in the Actions column.
      • To start multiple migration tasks at a time, select the tasks and click Start/Retry in the lower part of the Migration Tasks page. The selected tasks must be in the Ready, Stopped, or Error state.
      • To suspend a migration task in the Syncing state, click Pause in the Actions column.

What to do next

On the Migration Tasks page, wait until the migration task is completed. You can view the migration speed and remaining synchronization time. . 1236If the task enters the Completed state, the migration is successful. 127
  • If you set Resource Type to ECS Image, you can perform the following steps to create an ECS instance by using an image:
    1. Optional:Verify the migration result. This feature verifies whether the image generated by the migration task can create and start instances. This verification is based on the Operation Orchestration Service (OOS) template named ACS-SMC-CreateAndVerifyInstance provided by Alibaba Cloud.
      1. Click Verify Migration Result in the Actions column.
      2. In the dialog box that appears, read the verification process, and click Verify Now.

        You can also click Custom Verification Script to set the parameters.

      3. View the verification result in the Last Migration Result column.
        • Successful: indicates that the migration is successful. You can click View Output Parameter to check the details.
        • Failed: indicates that the migration failed. You can click View Cause to view the cause of failure and troubleshoot errors.

        You can also click the ... icon in the Actions column, and then click Check Verification History in the OOS Console to view the template history.

    2. Find the migration task and click Create Instance in the Actions column. list
    3. Set the parameters to create the destination instance. For more information, see Create an ECS instance by using a custom image.
    4. Connect to the instance and check the system of the destination server. For more information, see How can I check my system after migrating a Windows server? or How can I check my system after migrating a Linux server?
  • If you set Resource Type to ECS Instance, you can click View Destination Instance in the Actions column to go to the Destination Instance page.
  • If you set Resource Type to Container Image, you can use a container image to deploy applications. For more information, see Migrate source servers to Container Registry. smc docker
If the migration task enters the Error state, the migration failed. You must perform the following steps:
  1. Click View Logs in the Actions column to fix errors. For information about common errors and solutions, see SMC FAQ.
  2. On the Migration Tasks page, restart the migration task. The migration task resumes from the point where it was suspended.
    Note If the intermediate instance is released, you must create another migration task. For more information, see the "What can I do if I have released an intermediate instance by mistake?" section in SMC FAQ.