Server Migration Center:Migrate a server to Simple Application Server

Procedure

1. Log on to the SMC console.

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

3. Find the migration source for which you want to create a migration job and click Create Migration Job in the Actions column.

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

   The following table describes the parameters for creating a lightweight server migration job. You can use default values for the parameters that are not described in the table. For more information, see Create a server migration job.

   Parameter	Description
   Migration Job Type	The type of the migration job. After you select Server Migration, carefully read the migration instructions.
   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 Type	The type of the destination on Alibaba Cloud to which you want to migrate the source server. Set this parameter to Simple Application Server.
   Destination Region	The 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.
   Destination instance	The simple application server that is used as the destination instance. The storage system and operating system of the simple application server must be compatible with those of the source server. For example, you can migrate a Linux source server only to a Linux simple application server, and a Windows source server only to a Windows simple application server. Important During the migration, do not stop, start, restart, or release the simple application server. Otherwise, the migration fails. If the number of data disks on the simple application server is less than the number of data disks on the migration source, only some data disks on the migration source are migrated to the simple application server. If the disk size of the simple application server is smaller than that of the migration source, we recommend that you increase the disk size of the simple application server before you create the migration job. For more information, see Extend the data disk.
   Destination Disk Size (GiB)	The disk configurations of the destination simple application server. Configure the following parameters based on your business requirements: System disk System Disk: the size of the system disk of the simple application server. Unit: GiB. Valid values: 20 to 2048. The size of the destination system disk must be larger than the amount of data stored 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 indicates 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 of N: 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, Partition 0 is generated. Data disk Data Disk <0>: the size of the data disk of the simple application server. Unit: GiB. Valid values: 20 to 32768. If you select the Data Disk <N> check box, a destination data disk is generated. Only one data disk can be attached to a simple application server. The size of the destination data disk must be larger than the amount of data stored 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 parameters for data disks 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 FAQ topic. Block Replication SMC checks whether the migration source supports block replication for partitions. If the migration source does not support block replication for partitions, you cannot turn on Block Replication. 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, Block Replication 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. 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.

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

6. On the Migration Jobs page, wait until the migration job is complete. You can view the migration speed and remaining synchronization duration.

   

   • If the state of the migration job changes to Completed, the migration is successful.

     

     After the migration is complete, you can check whether the data is complete and whether the destination simple application server runs as expected. To do so, perform the following operations:

     1. In the Migration Result column of the migration job, click the simple application server ID.

        You are navigated to the Simple Application Server console.

     2. Log on to the simple application server. For more information, see Connect to a Linux server or Connect to a Windows server.

     3. Check the data of the simple application server. 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.

   • If the migration job is in the InError state, the migration failed. 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.