You can import multiple migration tasks at a time in the SMC console. SMC provides an Excel template to import task information.

Prerequisites

Before you import multiple migration tasks, make sure that the migration sources meet the following requirements:

Procedure

  1. Log on to the SMC console.
  2. In the left-side navigation pane, click Migration Tasks.
  3. On Migration Tasks page, click Import Migration.
  4. In the dialog box that appears, click Download Template.
    Download the Excel template to your local computer. addadad
  5. Configure migration tasks.
    1. Open the downloaded Excel template.
    2. Configure migration tasks. The following table describes the parameters of a migration task.
      Parameter Type Required Description
      SourceId String Yes The ID of the migration source. For more information, see Step 1: Import the information of a migration source.
      RegionId String Yes The ID of the destination Alibaba Cloud region. For more information, see Regions and zones.
      Name String No The name of the migration task. The name must meet the following requirements:
      • The name must be unique within an Alibaba Cloud region.
      • The name must be 2 to 128 characters in length and can contain letters, digits, colons (:), underscores (_), and hyphens (-). It must start with a letter rather than http:// or https://.
      Description String No The description of the migration task.

      The description must be 2 to 128 characters in length and can contain letters, digits, colons (:), underscores (_), and hyphens (-). It must start with a letter rather than http:// or https://.

      ImageName String No The name of the destination ECS image generated by SMC for the migration source. The name of the image must meet the following requirements:
      • The name must be 2 to 128 characters in length and can contain letters, digits, colons (:), underscores (_), and hyphens (-). It must start with a letter rather than http:// or https://.
      • The name must be unique within an Alibaba Cloud region. If you specify an image name that already exists in the destination region, the migration task ID is appended to the image name as a suffix. Example: ImageName_j-2zexxxxxxxxxxxxx.
      BandwidthLimit Integer No The maximum bandwidth of data transmission during migration. Unit: Mbit/s. Valid values: 0 to 999999.

      Default value: 0, which indicates that the bandwidth is not limited.

      CompressLevel Integer No The compression level of data in transmission during migration. Set the compression ratio based on your requirements. Valid values: 0 to 10. If you set the value to 0, data is not compressed during transmission.
      • 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.

      Default value: 7.

      Checksum Boolean No Specifies whether to verify data integrity by using a checksum. If you enable the checksum verification feature, data integrity is ensured whereas transmission speed may be reduced.

      Default value: false, which indicates that the checksum verification feature is disabled.

      ScheduledStartTime String No The time when the migration task is performed. The time must meet the following requirements:
      • The time must be specified in the ISO 8601 standard in the YYYY-MM-DDThh:mm:ssZ format. Example: 2021-01-01T12:00:00Z.
      • The value must be within 30 days after the current time.
      SystemDiskSize Integer Yes The system disk size of the destination ECS instance. Unit: GiB. Valid values: 20 to 500.
      Note 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 500 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.
      Disk<N>Size Integer No The data disk size of the destination ECS instance. Unit: GiB. Valid values: 20 to 32768.

      You can create destination data disks only for the data disks that already exist at the migration source. The <N> variable indicates the sequence number of the data disk. For example, if the migration source has two data disks, you must set the Disk1Size and the Disk2Size parameters. You can create up to 16 data disks.

      Note 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 400 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.
    3. Save and close the Excel template.
  6. Import the migration tasks.
    1. Return to the SMC console.
    2. In the left-side navigation pane, click Migration Tasks.
    3. On Migration Tasks page, click Import Migration.
    4. In the dialog box that appears, click Import Migration Tasks.
      smc2
    5. Select the Excel template, and then click Open.
    6. In the Import Migration Tasks dialog box, select the migration tasks that you want to import, and click OK.
      The following figure shows a sample list of imported migration tasks. smc1
      Note If the configurations of a migration task are invalid, the migration task cannot be selected. In this case, you can move the pointer over the Error message icon, fix the error based on the error message, and then re-import the migration task.

Result

If the message The migration task is imported. appears in the upper-right corner of the Migration Tasks page, the selected migration tasks are imported.

What to do next

Start the imported migration tasks.

  • If you specify the ScheduledStartTime parameter in the Excel template, the migration tasks automatically start at the specified time. You can check the migration progress on the Migration Tasks page.
  • If you do not specify the ScheduledStartTime parameter, you must manually start the migration tasks. For more information, see Step 2: Create and start a migration task.
Note For information about how to handle a migration task interruption or failure, see What can I do if a migration task is interrupted or fails?.