Server Migration Center:Quick migration of servers

Step 1: Import the migration source

Generate an activation code and a command in the SMC console as needed. Then, run the command on the migration source as an administrator to import the information about the source server.

1. Log on to the SMC console.

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

3. In the upper left corner of the Server Migration page, click General Quick Migration.

4. On the General Quick Migration page, click Generate.

   

5. Based on the source server operating system, click the Linux Shell or Windows Powershell tab, then click Copy to copy the activation code command.

6. Log on to the source server and paste and run the copied command as an administrator to import the information about the migration source.

   Linux server

   1. Log on to the Linux server.

   2. Paste and run the copied command as an administrator to import the information about the migration source.

      

      After the command is run, if a message similar to Import Source Server [s-bp18x8751kgz2oyh****] Successfully! is returned, the information about the migration source is imported.

   Windows server

   1. Log on to the Windows server.

   2. Open Windows PowerShell as an administrator.

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

      

      After the command is run, if a message similar to Import Source Server [s-bp19rlidl3mwuptc****] Successfully! is returned, the information about the migration source is imported.

7. Click Next Step.

   Note

   The system will automatically check whether the migration source is imported. If the migration source is not imported, you cannot proceed to the next step.

Step 2: Configure migration parameters

After importing the migration source, you can configure migration parameters as needed and start the migration.

1. Configure basic information and advanced parameters based on the following information:

   The following table describes the parameters.

   Basic Information Configuration

   Parameter	Description
   Migration Job Name	Optional. The name of the migration job.
   Job Description	Optional. The description of the migration job.
   Destination Type	Required. The type of the destination on Alibaba Cloud to which you want to migrate the source server. ECS Image You can migrate the source server to an ECS image and then create an ECS instance by using the image. If you set the Destination Type parameter to ECS Image, you must also configure the following parameters: Destination Region: the Alibaba Cloud region to which you want to migrate the Tencent Cloud Lighthouse instance. For more information about regions, see Regions and zones. Image Name: the name of the destination ECS image to be generated by SMC for the migration source. ECS Instance You can migrate the source server to an ECS instance that you have purchased. The storage system and operating system of the destination ECS instance must be compatible with those of the source server. Storage space: The storage space of the disks on the destination ECS instance must be larger than or equal to that on the source server. The disks include the system and data disks. Important If the disk size of the destination instance is smaller than that of the migration source, we recommend that you increase the disk size of the destination instance before you create the migration job. For information about how to resize disks online, see topics under Resize cloud disks. If the number of data disks on the destination instance is less than that on the migration source, only some data disks on the migration source are migrated to the destination instance. Security group: The ports enabled for the security group to which the destination ECS instance belongs must be the same as those of the source server. For more information, see Add a security group rule. Bandwidth: We recommend that you increase the bandwidths of the source server and destination instance as much as possible to facilitate migration. For more information, see Estimate the time required for migration and test the data transfer speed. If you set the Destination Type parameter to ECS Instance, you must also configure the following parameters: Destination Region: the Alibaba Cloud region to which you want to migrate the source server. For more information about regions, see Regions and zones. Destination Instance: the destination ECS instance to which you want to migrate the source server. Important During the migration, do not stop, start, restart, or release the destination instance. Otherwise, the migration fails. Simple Application Server You can migrate the Tencent Cloud Lighthouse instance to an Alibaba Cloud simple application server that you have purchased. The storage system and operating system of the Alibaba Cloud simple application server must be compatible with those of the Tencent Cloud Lighthouse instance. Storage space: The storage space of the disks on the Alibaba Cloud simple application server must be larger than or equal to that on the Tencent Cloud Lighthouse instance. The disks include the system and data disks. Important If the disk size of the destination instance is smaller than that of the migration source, we recommend that you increase the disk size of the destination instance before you create the migration job. For more information, see Upgrade a simple application server and Extend a data disk. If the number of data disks on the destination instance is less than that on the migration source, only some data disks on the migration source are migrated to the destination instance. Security group: The ports enabled for the security group to which the Alibaba Cloud simple application server belongs must be the same as those of the Tencent Cloud Lighthouse instance. For more information, see the "Manage a firewall" section of the Manage the firewall of a simple application server topic. Bandwidth: We recommend that you increase the bandwidths of the source server and destination instance as much as possible to facilitate migration. For more information, see Estimate the time required for migration and test the data transfer speed. If you set the Destination Type parameter to Simple Application Server, you must also configure the following parameters: Destination Region: the Alibaba Cloud region to which you want to migrate the Tencent Cloud Lighthouse instance. For more information about regions, see Regions and network connectivity. Destination Instance: the Alibaba Cloud simple application server to which you want to migrate the source server. Important During the migration, do not stop, start, restart, or release the destination instance. Otherwise, the migration fails. Container Image Servers running only on x86-architecture Linux operating systems support migration to container images. If you set the Destination Type parameter to Container Image, you must also configure the following parameters: Destination Region: Refers to the Alibaba Cloud region where your source server will be migrated to. For more information about regions, see Regions and zones. Namespace: Select the namespace for storing the container image repository generated by the migration. For more information about creating a namespace, see Manage namespaces and resource quotas. Repository: Select the name of the repository where the container image generated by the migration will be stored. For more information about creating an image repository, see Create a repository and build images. Version: Enter the version information for the container image generated by the migration. RAM Role: Select the instance role bound to the intermediate instance. For more information about creating a RAM role, see Create a RAM role for a trusted Alibaba Cloud service.
   Modify Disk Partition	Determine whether to enable Modify Disk Partition based on your needs. This feature is only supported in SMC client 2.8.0 or above. For more information, see Use the SMC client. Not enabled: By default, the disk partition structure of the destination system are the same as those of the migration source. Enabled: You can adjust the destination disk partition structure, including partition size and order, transfer method, whether to enable LVM, and other configurations. The parameter descriptions for the disk partition structure are as follows. Configure disks 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. Data Disk <N>: the size of the data disk of the destination instance. Unit: GiB. Valid values: 1 to 32768. The variable <N> indicates the serial number of the data disk. If the disk is migrated to the destination instance, N is the ID 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. If there are no mount targets under the data disk or if all mount targets are not migrated, the data disk will not be migrated. LVM: Logical Volume Manager (LVM) is a mechanism for managing disk partitions in Linux systems. LVM is more flexible than traditional disk partitions and allows for dynamic adjustment of disk space. You can select whether to enable LVM based on your needs. After enabling LVM, the destination will automatically rebuild the disk with an LVM structure. Example description: For each destination disk where LVM is enabled, the system will create one Physical Volume (PV) and its corresponding Volume Group (VG). On the VG, a number of Logical Volume Manager (LVM) corresponding to the mount targets are created. By default, the VG name is vgX (where X is the serial number of the disk), and the LVM name is lvX (where X is the serial number of the LVM). An example is provided in the following figure. Important LVM is not supported in the following scenarios: When the migration source is a Windows system. When the system disk does not have a boot partition. After enabling LVM, the feature does not take effect in the following scenarios: The migration source does not support lvm2 or the lvm2 package is not installed. The migration source is a Debian system with a kernel version of 3.x or earlier, and disks with XFS file systems are mounted. Configure mount targets Whether to Migrate: You can select whether to migrate the mount target based on your business needs. Enable Block Replication: Enabling block replication can effectively improve the stability of migration transmission speed while ensuring consistency with the source partition structure. However, the partition size cannot be modified. SMC determines whether to support enabling block replication based on the migration source disk partition status. If the migration source does not support block replication for partitions, the Enable Block Replication switch cannot be turned on, and default file replication method is used, allowing partition size modification. If the migration source supports block replication for partitions, the Enable Block Replication switch is enabled by default to achieve partition-level disk migration. Note When the migration source is a Windows operating system, the block replication feature is enabled by default and cannot be disabled. If LVM is enabled on the disk and the partition size is not an integer multiple of 4 MiB, block replication does not take effect, and file replication is used for data transfer. Set partition size: When block replication is not enabled, you can set the partition size based on your needs, but the sum of partition sizes cannot exceed the size of the disk they belong to. Note If the size of disks of the destination instance do not match that of the migration source disks, the migration task cannot be created. In this case, the system will automatically adjust the mount target positions to meet the disk size requirements. If the requirements cannot be met after the adjustment, handle the issue as prompted. You can also manually drag and drop mount targets to meet disk size requirements. However, drag-and-drop is not supported for partitions of type boot or system. The specific operations are as follows: Move your pointer over before the mount target. Use your pointer to drag the mount target to another disk.
   Migration Test	This parameter is displayed only when the Destination Type parameter is set to either ECS Image or ECS Instance. 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 enabled. 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 contain important data. For more information, see Configure a migration test.
   Execution Method	Select an execution method based on whether Migration Test is turned on. When Migration Test is turned on Test Only: The system performs only the migration test. After the migration test is complete, you must manually start the server migration job. Test and Migrate: The system performs the migration test. After the migration test is complete, if no test items are in the Critical state, the system automatically starts the server migration job. This is the default value. When Migration Test is turned off 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 job is 10 minutes after the job is created. Create Only: After the migration job is created, you must click Start Migration Job in the Actions column to manually start the migration job.
   Automatic Incremental Synchronization	This parameter is displayed only when the Destination Type parameter is set to either ECS Image or ECS Instance. Specifies whether SMC automatically synchronizes incremental data of the migration source to Alibaba Cloud. By default, this feature is disabled. If you enable this feature, you must configure the following parameters: Synchronization Interval: the interval at which SMC automatically synchronizes incremental data to Alibaba Cloud. Maximum Reserved Images: the maximum number of images that can be retained during incremental data synchronization. SMC automatically synchronizes incremental data to Alibaba Cloud at the specified interval. For more information about the best practices for incremental data synchronization, see Migrate incremental data from a server. If you disable this feature, incremental data is not synchronized.
   Enable Migration Template	This parameter is displayed only when the Destination Type parameter is set to ECS Image. The migration template is used to preset parameters for migration jobs, and the template parameters are automatically filled in when the migration starts. For more information about setting the migration template, see Configure the migration template.

   Advanced Settings

   If you need to set parameters such as network type and transmission speed limit, click Advanced Settings to configure advanced parameters.

   Parameter	Description
   Network Type	The type of network that is used to migrate data from the source server to the intermediate instance. By default, data is migrated over the Internet. During the 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. Public Network (default value) 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 a VPC or vSwitch, SMC creates an intermediate instance that connects to the VPC and vSwitch 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, or SAG to connect a migration source to a VPC. For more information, see Connect a data center to a VPC.
   Transmission Speed Limit	The maximum network transfer speed during the migration. Unit: Mbit/s. If you set the Compression Ratio parameter to a value greater than 0, the actual network transfer speed, which is the transfer speed of compressed data, is lower than the speed displayed in the Real-time Migration Status column.
   Compression Ratio	The 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 CPU resources of the migration source. Valid values: 0 to 10. Default value: 7. A value of 0 indicates that data is not compressed.
   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.
   License Type	This parameter is displayed only when the Destination Type parameter is set to either ECS Image or ECS Instance. The license type. Valid values: Alibaba Cloud: the Microsoft license provided by Alibaba Cloud. For more information, see the What Windows Server licenses does Alibaba Cloud support? section of the "FAQ" topic. This is the default value. BYOL: SMC allows you to bring your own license (BYOL). You can bring your own Microsoft license or register with Red Hat Cloud Access. For more information, see the Is BYOL supported when I migrate servers by using SMC? section of the "FAQ" topic.
   Image Check	This parameter is displayed only when the Destination Type parameter is set to ECS Image. 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.
   Tag	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.
   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 Destination Type parameter 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 job fails to be created. If you do not specify an instance type, SMC automatically creates an intermediate instance. Important Do not stop, start, restart, or release the intermediate instance during the migration to prevent migration failures.

2. Click Start.

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

4. In the General Quick Migration dialog box, click View Now to view the real-time migration status.

   If you enable a migration test, SMC will first perform the test and proceed with the migration operation after the migration test is passed.

   If the migration test fails, you need to review the test report, fix the test items that are in the Critical state, and retry the migration test. For more information, see Configure a migration test.

   The amount of time required for data transmission is subject to factors such as the data size of the migration source and network bandwidth. Wait until the migration job is complete.

   When the migration job is in the Synchronizing state, the Speed and Time Remaining for Synchronization parameters are displayed in the Real-time Migration Status column:

   • Speed: the amount of data that is migrated per second, which indicates the transfer speed of uncompressed data. If you set the Compression Ratio parameter to a value greater than 0, the actual network transfer speed, which is the transfer speed of compressed data, is lower than the displayed speed.

   • Time Remaining for Synchronization: the remaining synchronization time calculated based on the current speed by using the following formula: Time remaining for synchronization = (Total data size - Transferred data size)/Speed.

   

   When the migration job is in the Synchronizing state, you can perform the following operations as needed:

   • Modify the migration job: In the Actions column, click Modify Migration Job to modify the Transmission Speed Limit, Compression Ratio, and Checksum Verification parameters.

   • Pause the migration job: In the Actions column, click Pause Migration Job.

Verify the migration result

• When the Real-time Migration Status is Completed, it indicates that the migration is successful.

  Migrate servers to ECS Image

  After the migration is complete, an Alibaba Cloud custom image is generated. You can use your pointer to slide the scrollbar at the bottom to the right and click View Report in the Migration Deliverables column to view the check result of the image. For more information, see View the image check results step of the "Configure image check" topic.

  

  (Recommended) Manually verify the migration result

  You can click Create Instance in the Actions column to go to the ECS instance creation page in the ECS console. The custom ECS image created by the migration job is selected by default for you to create an ECS instance. For more information, see Create an instance by using a custom image.

  Use the automatic migration result verification feature

  Note

  To use this feature, you must install the Cloud Assistant Agent in your instance, and the system version of the instance must support this feature. For more information, see Install Cloud Assistant Agent.

  This feature uses the ACS-SMC-CreateAndVerifyInstance template provided by Alibaba Cloud CloudOps Orchestration Service (OOS) to automatically verify whether the image generated by the migration job can be used to create an ECS instance and whether the ECS instance can start as expected.

  1. 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. In the Verify Migration Result column, view the verification result. Valid values:

     • Verified: indicates that the migration is successful. You can click View Report to check the verification result.

     • Not Verified: indicates that the migration failed. You can click View Cause to troubleshoot the failure.

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

  Migrate servers to ECS instances and simple application servers

  If you set the Destination Type parameter to ECS Instance for the migration job, you can click View Destination Instance in the Actions column to go to the details page of the destination ECS instance to verify the migration result.

  Migrate servers to containers

  After a successful migration, an Alibaba Cloud container image is generated. You can deploy container applications through the container image. Perform the following steps:

  1. Create an ACK cluster. For more information, see Create an ACK dedicated cluster.

  2. In the Actions column of the migration source, click Deploy Application. The application creation page appears.

  3. Create an application. For more information, see Create a stateless application by using a Deployment.

  4. After the server is migrated, you must verify the data to ensure data integrity and correctness. For more information, see the "How do I check my system after I migrate a Linux server?" section of the FAQ topic.

     Note

     If a domain name has been bound to the source server, the public IP address of the server is changed after the migration. In this case, you must resolve the domain name to the new public IP address of the server For more information, see Add an A record for a website domain name.

  After migrating servers, to ensure normal business operations, you need to perform the following operations:

  • Verify the integrity and correctness of the data. For more information, see 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? .

  • Manually start the applications and services after the migration if automatic start is not enabled for the applications and services on the source server.

  • The IP address changes after the migration job is complete. Change the IP address of the server after the migration if your business involves IP address configuration.

    • If a domain name has been bound to the source server, the public IP address of the server is changed after the migration. In this case, you must resolve the domain name to the new public IP address of the server. For more information, see Add an A record for a website domain name.

    • 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 Primary private IP address.

• If Error is displayed in the Real-time Migration Status column, the migration failed.

  In this case, you need to perform the following operations:

  1. Click Troubleshoot Errors in the Actions column and fix the failure based on the error code and error message. For more information, see FAQ about Server Migration Center (SMC) and Errors occurred during a server migration.

  2. In the migration source list, click Retry Migration Job.

     The migration job resumes from the point where it was suspended.

     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.

Clear resources

• Migrate servers to ECS images and container images

  During the migration, SMC creates a temporary pay-as-you-go intermediate instance named No_Delete_SMC_Transition_Instance within the destination Alibaba Cloud account. The method to clear resources depends on whether the migration is successful.

  • If the migration is successful, the intermediate instance is automatically released. No manual operation is required.

  • If the migration failed, the intermediate instance is not automatically released and incurs fees as long as the migration job exists. You can release the intermediate instance in one of the following ways to reduce costs:

    • If you no longer need the migration job, click the ID the migration job. On the job details page, click > Clear migration task in the Actions column in the Migration Jobs section to delete the migration job and release the intermediate instance at a time.

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

• Migrate servers to destination instances

  During the migration, SMC creates a temporary pay-as-you-go intermediate cloud disk named SMC_Temp_Disk in the destination instance. The method to clear resources depends on whether the migration is successful.

  • If the migration is successful, the intermediate cloud disk is automatically released. No manual operation is required.

  • If the migration failed, the intermediate cloud disk is not automatically released and incurs fees as long as the migration job exists. You can release the intermediate cloud disk in one of the following ways to reduce costs:

    • If you no longer need the migration job, click the ID of the migration job. On the job details page, click > Clear migration task in the Actions column in the Migration Jobs section to delete the migration job and release the intermediate cloud disk at a time.

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