(Optional) Evaluating Migration Risks
You can evaluate migration risks by identifying potential issues such as compatibility conflicts, firmware mismatches, and specification differences. Check the risks using Table 1 or use the MgC migration risk evaluation function by referring to Assessing Migration Risks.
| Category | Risk | Countermeasure |
| TB-level data migration | Restarting a full migration task may take even longer, as it requires re-verification and could extend your planned timeline. | Do not suspend a task of migrating massive volumes of data, for example, migrating a host with nearly a TB of data. |
| CPU architecture of a server | Must be x86 or x86_64 (AMD64). | If the source server uses the Arm architecture, refer to Kunpeng Professional Services on Huawei Cloud. |
| UEFI-booted server | To migrate such a server, the target one must be created from private images with UEFI mode enabled. | Prepare such target servers in advance. |
| Incremental migration required for a source server | Evaluate whether incremental migration is required for the source server. | If required, perform an incremental migration test before service cutover to prevent incremental migration failures, such as agent exceptions. Check the incremental files on the target server. |
| HA applications on the source server | Evaluate whether HA is configured for applications on the source server. | Configure HA and perform anti-affinity deployment after the migration. |
| Small file migration | If the source server has a large number of small files, migration is slow. | Perform a test to evaluate the migration time window. |
| Source server application | The source server may contain clusters, such as self-built databases, containers, and middleware, with an active/standby deployment. Direct migration of the source server could lead to service downtime at the target. | It is recommended to redeploy self-built databases, containers, and middleware clusters and configure the active/standby mode on the target server, and then proceed with data migration. |
| ECS constraints | The ECS usage precautions and constraints must be met. | For details, see ECS Constraints. |
| VirtIO driver | For Windows, verify if the VirtIO driver is installed by pressing Win+X, selecting Device Manager, and searching for VirtIO-related devices. If the VirtIO driver is not installed, Huawei Cloud network communication will fail. | Install the VirtIO driver. If the OS does not support the VirtIO driver, migration cannot be performed. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot