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

Background information

During server migration, 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 accelerates data transmission during migration.

Procedure

  1. Log on to the SMC console.
  2. In the left-side navigation pane, click Migration Sources.
  3. Find the migration source and click Create Migration Job 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 the How do I find a migration source in the SMC console? section of the SMC FAQ topic. Obtain the ID of the migration source
  4. In the Create Migration Job dialog box, configure the parameters and click Create.
    SMC supports server migration and operating system migration. You can select a migration task type based on your business requirements. For more information about best practices, see Migrate an operating system.
    The following table describes the parameters that you can configure to create a server migration task.
    ParameterDescription
    Migration Job TypeThe type of the migration task. After you select Server Migration, read the migration instructions carefully.
    Basic Settings
    Destination RegionThe Alibaba Cloud region to which you want to migrate your source server. This parameter is required. For more information about regions, see Regions and zones.
    Migration Job NameThe name of the migration task.
    Note The task name must be unique within an Alibaba Cloud region.
    Job DescriptionThe description of the migration task.
    Destination Disk SizeThe disk configurations of the destination server. adadConfigure the following parameters based on your business requirements:
    • Enable Block Replication
      • If you select Enable Block Replication, stable data transmission is ensured. The block-level replication feature also ensures that the source and destination disks use the same partitioning scheme. You cannot modify the size of each partition on the destination disk. After you select Enable Block Replication, the 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 on the destination disk.
      Note If your source server runs Windows, block-level replication is enabled by default. Do not disable it.
    • System Disk
      • System Disk: the system disk size of the destination Elastic Compute Service (ECS) instance. Unit: GiB. Valid values: 20 to 500. 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 system disk based on the partitioning scheme of the source system disk. Unit: GiB. Valid values: 0 to 14. N indicates the serial number of the partition. For example, if the system disk of the migration source has only one partition, Partition0 is generated.
      • Enable Block Replication: This switch is displayed only if you select Enable 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-level replication for partitions, you cannot turn on the switch.
        • If the migration source supports block-level replication for partitions, you can turn on the switch to migrate disk data at the partition level.
    • Data Disk<N>
      • 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 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: 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, Partition0 is generated.
      • Enable Block Replication: This switch is displayed only if you select Enable 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-level replication for partitions, you cannot turn on the switch.
        • If the migration source supports block-level replication for partitions, you can turn on the switch to migrate disk data at the partition level.
      Note Data Disk<N> is displayed only if the migration source has a data disk. For more information, see the Why are the data disk parameters of a migration source not displayed in the Create Migration Job dialog box? What do I do? section of the SMC FAQ topic.
    Destination TypeThe type of the destination on Alibaba Cloud to which you want to migrate the migration source. Valid values:asads5
    • ECS Image: You can migrate the source server to an ECS image and then create an ECS instance by using the image.
    • ECS Instance: You can migrate the source server to an ECS instance that you have purchased. The storage system and operating system of the source server must be compatible with those of the ECS instance.
      Important
      • After the migration task is created, all original data in the destination instance is deleted. If the destination ECS instance contains important data, we recommend that you do not migrate the source server directly to the destination instance. In this case, we recommend that you set the Destination Type parameter to ECS Image and create an ECS instance by using the image. For more information about how to migrate a source server to a destination instance, see Migrate servers to ECS instances.
      • After the migration is complete, the data disks on the destination ECS instance are released, and the automatic snapshots of the data disks are deleted and cannot be recovered. You can manually disable the Delete Automatic Snapshots While Releasing Disk feature to retain the snapshots. For more information, see Delete automatic snapshots while releasing a disk.
    • Container Image: You can migrate the source server to Container Registry. Then, you can deploy containerized applications in Container Registry at low costs.
    The following section describes the parameters that you can configure for each type of destination.
    • ECS Image
      Parameters:
      • Image Name: 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: the type of the license. Valid values:
        • Alibaba Cloud: the Microsoft license provided by Alibaba Cloud. For more information, see SMC FAQ.
        • BYOL: SMC allows you to bring your own license (BYOL). You can use your own Microsoft or Red Hat license to migrate a server to Alibaba Cloud. For more information, see SMC FAQ.
      • Automatic Incremental Synchronization: specifies whether SMC automatically synchronizes the incremental data of 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.
          • 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, see Migrate incremental data from a source server.
        • If you disable this feature, incremental data is not synchronized.
    • ECS Instance
      Note The storage and operating systems of the source server and destination instance must be compatible. For more information about best practices, see Migrate servers to ECS instances.
      Parameters:
      • Destination Instance: Select an ECS instance as the destination instance.
      • License Type: the type of the license. Valid values:
        • Alibaba Cloud: the Microsoft license provided by Alibaba Cloud. For more information, see SMC FAQ.
        • BYOL: SMC allows you to bring your own license (BYOL). You can use your own Microsoft or Red Hat license to migrate a server to Alibaba Cloud. For more information, see SMC FAQ.
      • Automatic Incremental Synchronization: specifies whether SMC automatically synchronizes the incremental data of 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.
          • 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, see Migrate incremental data from a source server.
        • If you disable this feature, incremental data is not synchronized.
    • Container Image
      Note
      Parameters:
      • Namespace: the namespace of the destination container image.
      • Repository Name: the name of the repository that stores the destination container image.
      • Version: the version of the destination container image.
      • RAM Role: the RAM role that is assigned to the intermediate instance.
    Execution MethodThe method that is used to run the migration task. Valid values:
    • Run Now: The migration task starts immediately after it is created.
    • Run Later: The migration task 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: After the migration task is created, you must manually start the task.

    Default value: Run Now.

    Tags and Network (Optional)
    Migration Job TagsThe 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 TypeThe type of the network that is used to migrate data to the intermediate instance. During migration, SMC creates an intermediate instance that connects to a vSwitch in a virtual private cloud (VPC). If you select Public Network, a public IP address is assigned to the intermediate instance. adda
    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 migration tasks. This improves the usage of VPC resources. In this case, 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 if you do not specify a VPC or a vSwitch. To raise the VPC quota, submit a ticket.
    • VPC: SMC migrates data to the intermediate instance over a VPC. If you select VPC, you must specify a VPC and a vSwitch and make sure that the migration source can connect to the VPC.
      Note If your server in a data center, your VM, or your cloud host can connect to a VPC, we recommend that you select this network type to migrate data. Compared with migration over the Internet, migration over a VPC is more efficient and stable. You can use VPN Gateway, Express Connect, and Smart Access Gateway to connect a migration source to a VPC. For more information, see Connect a data center to a VPC.
    Advanced Settings (Optional)
    Checksum VerificationThis feature enhances the verification of data consistency between the migration source and the destination instance. However, this may slow down data transmission.

    By default, this feature is disabled.

    Transmission Speed LimitThe maximum bandwidth for data transmission during migration. Unit: Mbit/s.
    Compression RatioThe 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.

    Intermediate Instance TypeThe type of the intermediate instance. Select an intermediate instance type based on your business requirements. This parameter is displayed only if the Destination Type parameter is set to ECS Image or Container Image.
    • If you specify an instance type, SMC creates an intermediate instance of the specified type. If the specified instance type is unavailable, the migration task fails to be created.
    • If you do not specify an instance type, SMC automatically selects an instance type to create an intermediate instance.
  5. Start the migration task.
    Note If the Execution Method parameter is set to Run Now, skip this step. If the Execution Method parameter is set 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 Jobs.
    2. Find the migration task and click Run in the Actions column.
      • To start multiple migration tasks at a time, select the tasks and click Start or Retry in the lower part of the Migration Jobs page. The selected tasks must be in the Ready, Stopped, or InError state.
      • To stop a migration task in the Synchronizing state, click Stop in the Actions column.
  6. On the Migration Jobs page, wait until the migration task is complete. You can view the migration speed and remaining synchronization duration. 1236
    If the migration task enters the Completed state, the migration is successful. daasda5862

What to do next

OperationDescription
Verify the migration resultThis feature verifies whether the image generated by the migration task can be used to create and start instances. This verification is based on the Operation Orchestration Service (OOS) template named ACS-SMC-CreateAndVerifyInstance provided by Alibaba Cloud.
  1. Find the migration task and click Verify Migration Result in the Actions column.
  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. View the verification result in the Latest Verification Result column.
    • Successful: indicates that the migration is successful. You can click Show Output Parameters to check the details.
    • Failed: indicates that the migration failed. You can click View Cause to view the cause of failure and troubleshoot issues.

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

View the destination instanceIf you migrate an operating system or set the Destination Type parameter to ECS Instance, you can find the migration task and click View Destination Instance in the Actions column to view the details of the destination instance.
Deploy a container applicationIf you set the Destination Type parameter to Container Image, you can use a container image to deploy applications. For more information, see Migrate source servers to Container Registry. smc docker
View the details of the migration taskOn the Migration Jobs page, click the ID of the migration task to view the details of the migration task.
Troubleshoot migration issues
If the migration task enters the InError state, the migration failed. In this case, you can perform the following steps:
  1. Find the migration task and click View Logs in the Actions column to view logs and fix errors. For information about common errors and solutions, see SMC FAQ.
  2. On the Migration Jobs page, restart the migration task. The migration task resumes from the point where it was stopped.
    Note If the intermediate instance is released, you must create another migration task. For more information, see the What do I do if I release an intermediate instance by accident? section of the SMC FAQ topic.