After you import the information of a migration source, Server Migration Center (SMC) automatically generates a record of 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 a 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 of the 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 improves the data transmission rate during migration.
- You can use the migration template provided by SMC to create multiple migration tasks at a time. For more information, see Import multiple migration tasks by using an Excel template.
Procedure
What to do next
- On the Migration Tasks page, wait until the migration task is complete. If the task enters the Completed state, the migration is successful.
- If you set Target Image Type to ECS Image, you can perform the following steps to
create an ECS instance by using an image:
- 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.
- Click Verify Migration Result in the Actions column.
- 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.
- 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.
- Click Create Instance in the Actions column.
- Set the parameters to create the destination instance. For more information, see Create an ECS instance by using a custom image.
- Connect to the destination instance and check its system. For more information, see the "How do I check my system after I migrate a Windows server?" or "How do I check my system after I migrate a Linux server?" section of the SMC FAQ.
- 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.
- If you set Target Image Type to ECS Instance, you can click View Target Instance in the Actions column to go to the Target Instance page.
- If you set Target Image Type to Container Image, you can use a container image to
deploy applications. For more information, see Migrate source servers to Container Registry.
- If you set Target Image Type to ECS Image, you can perform the following steps to
create an ECS instance by using an image:
- If the migration task enters the Error state, the migration failed. You must perform the following steps:
- Click View Logs in the Actions column. For information about common errors and solutions, see SMC FAQ.
- 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 of the SMC FAQ.