Configure a migration test

Limitations

You can perform a migration test only in the following migration scenarios:

• Migrating a server to an ECS image or an ECS instance.

• Migrating a Linux operating system.

Procedure

1. Log on to the SMC console.

2. Navigate to the correct page based on your migration scenario.

   • Server migration:

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

   • OS migration:

     In the left-side navigation pane, choose Cloud Migration > OS Migration.

3. Import a migration source and configure a migration job. For more information, see Migrate servers to ECS and operating system migration (Linux).

   The following tables describe the key parameters for configuring a migration test.

   Server migration

   Parameter	Description
   Migration Job Type	After you select Server Migration, carefully read the on-screen instructions.
   Destination Type	ECS image ECS Image Converts the source server into a custom image. You can then use this custom image to create an ECS instance and complete the migration. The following parameters are available: Destination Region: The Alibaba Cloud region where the custom image will be created. This parameter is required. Regions and zones. Image name prefix: The prefix of the custom image name that SMC generates for the migration source. ECS instance If you have already purchased a destination instance, such as an ECS or a Simple Application Server instance, you can migrate the source server directly to it. Ensure that the storage, operating system, and other configurations of the source server are compatible with the destination instance. Warning During the migration test, snapshots are created for all cloud disks of the destination ECS instance. If the test fails or the Test Only is set to Test Only, the snapshots are automatically rolled back after the test completes. The destination ECS instance is unavailable during the test, and any data written to it during this period will be lost. Ensure that the destination ECS instance does not contain any important data. The following parameters are available: Target Region: The destination region for your source server. This parameter is required. For more information about regions, see regions and zones. Destination Instance: Select an ECS instance to use as the destination.
   Migration Test	A migration test simulates your migration to assess its feasibility and risks, reducing potential issues and losses during the actual migration. This test helps you quickly identify potential issues and provides recommended solutions to improve the migration success rate. By default, Migration Test is enabled.
   Execution Method	Select an execution method. By default, Test and Migrate is selected. In this example, Test Only is selected. Test Only: Creates only a migration test job. After the test completes, you must manually start the server migration job. Test and Migrate: After the migration test completes, the system automatically starts the server migration job if no test items are in the Critical state.

   Operating system migration

   Operating system migration supports two methods: fast migration and step-by-step migration. Currently, only step-by-step migration supports migration tests.

   Parameter	Description
   Migration Job Type	Select OS Migration.
   Current Operating System	The current operating system is displayed by default and cannot be modified. Example: CentOS 7.
   Destination Operating System	Select a destination operating system from the drop-down list. Example: Alibaba Cloud Linux 3.
   Migration Test	A migration test simulates your migration to assess its feasibility and risks, reducing potential issues and losses during the actual migration. This test helps you quickly identify potential issues and provides recommended solutions to improve the migration success rate. By default, Migration Test is enabled. Warning If the "Migration Test" feature is enabled, the test process creates a basic disk snapshot of the ECS cloud server. If "Test and Migrate" is not enabled or the test fails, the snapshot is automatically rolled back after the test is complete. Because the snapshot is created at the start of the current test, any data generated during this period will be lost.
   Execution Method	Select an execution method. By default, Test and Migrate is selected. In this example, Test Only is selected. Test Only: Creates only a migration test job. After the test completes, you must manually start the operating system migration job. Test and Migrate: After the test is complete, the system automatically starts the OS migration job if no test items are in the Critical state.

4. Click Start Migration, and then click Got It in the confirmation dialog box.

   The system automatically starts the migration test. Wait for the test to complete.

   • Server migration test

     • If ECS Image is set to ECS Image, the migration test takes about 5 minutes.

     • If ECS Instance is set to ECS Instance, snapshots are created for all cloud disks of the instance during the test. The duration of the test depends on factors such as the size of the instance's cloud disks and the amount of data.

   • Operating system migration test

     During the migration test, snapshots are created for all cloud disks of the instance. The duration of the test depends on factors such as the size of the instance's cloud disks, the amount of data, and the size and number of software packages in the operating system. For example, if the instance has only a 40 GiB system disk, the migration test takes about 15 minutes.

   The following list describes the migration test statuses:

   • : The migration test is in progress.

   • : No issues were found.

   • : One or more Warning items were found, but no Critical items were found.

   • : One or more Critical items were found, or the test report is incomplete.

   After the migration test is complete, the Real-time Migration Status column for the migration source displays Passed.

5. Based on the test results, start the migration job or retry the test.

   Important

   For an operating system migration job, if the migration test fails or the Test Only is set to Test Only, the instance must be stopped to roll back the snapshots. This causes the SMC client to go offline. After the rollback, Cloud Assistant automatically restarts the SMC client. If Cloud Assistant fails to restart the client, the migration source remains offline. In this case, you cannot start the job or retry the test. You must manually log on to the ECS instance to start the client. For more information, see Manage the SMC client.

   • If the test status is or , you can click Start Migration Job in the Actions column to start the migration.

   • If the test status is , you must view the report, fix all Critical items, and then click Retry Test.

6. View the migration test report.

   This step describes how to view the migration test report if you set the Execution Method to Test Only. Alternatively, you can click the migration source ID to open its details page, navigate to the Migration Test section, and click View Report.

   1. On the Migration Job page, find the target migration job and click View Report in the Real-time Migration Status column.

   2. In the Migration Drill Report panel, view the report details.

      The following list describes the statuses of test items:

      • Critical: Indicates an issue that is highly likely to cause migration failure. We strongly recommend that you fix this issue.

      • Warning: Indicates an issue that may affect the migration. Review the details to determine if a fix is needed.

      • Passed: No issues were found.

      • Not Tested: The test item was not run because it was not applicable or its prerequisites were not met.

        Note

        To run checks for a Windows server migration, the following requirements must be met. If they are not met, all test items under Source environment check are marked as Not Tested.

        OS architecture	OS version	OS configuration
        x86_64	Windows Server 2008 or later	PowerShell 3.0 or later

      Based on the details and recommended solutions for each test item, perform the required actions.

      The following is an example of a server migration test report:

      The top of the report displays the migration job ID, report ID, and start time, and a summary of the number of Critical and Warning items. The Migration performance test section shows metrics such as total data volume, Iperf network test speed, throughput, IOPS, estimated synchronization time, estimated processing time, and estimated total migration time, and provides a pass/fail conclusion. The Test item details section includes three checks: Source environment check, Destination environment check, and Data synchronization test, with each showing the number of passed and skipped checks.

7. (Required) If the report contains Critical or Warning items, fix them based on their details and recommended solutions. For more information, see Migration test item descriptions.

8. (Optional) In the Actions column for the migration job, click Modify Migration Job to adjust the job parameters as needed.

   Note

   You cannot modify an operating system migration job.

9. (Required) After you fix the Critical and Warning items, click Retry Test in the Actions column for the migration job.

   Note

   You can click Retry Test only when the migration source has a Migrating status and the migration job has a Ready or Test Failed status.