Migrating Servers Across AZs on Huawei Cloud

Scenario

This section describes how to use MgC to quickly migrate ECSs from AZ 1 to another AZ in the CN South-Guangzhou region of Huawei Cloud. This practice applies to migration of fewer than 30 ECSs in a single batch across AZs within a region. You only need to specify a resource group name, and MgC takes care of all the rest, from resource discovery, collection, and assessment to migration.

Preparations

You need to prepare a Huawei account or an IAM user that can access MgC. For details, see Preparations.

Procedure

1. Log in to the MgC console.
2. In the navigation pane on the left, choose Overview.
3. In the Process Flow area, click the Cross-AZ Migration tab. In the Automated Process area, click Get Started.

   

4. In the displayed dialog box, specify an application name and select the target AZ you want to migrate to.
5. Click Create and Run. MgC will automatically collect information about servers in the selected source AZ under the current account, creates an application, adds the discovered servers to the application, and starts the assessment process.
6. After the assessment process is complete, click Close to configure the workflow.
7. Configure the workflow parameters listed in Table 1.

   Table 1 Parameters required for configuring a workflow

   Area	Parameter	Description
   Workflow Details	Name	Enter a workflow name.
   	Description	Enter a workflow name.
   Application	Application	Select the application defined in Step 4.
   Migration Settings	Region	Select the region the source AZ belongs to. By default, the value is CN South-Guangzhou and cannot be modified.
   	Target AZ	Select the AZ you want to migrate to. The configuration must be the same as that of the created application.
   	Target Network	Only Retain original is available.
   	Target Server	Create now. MgC creates backups and images for source servers, and uses the images to create target servers immediately after the workflow runs.
   	Stop Target Server	If you select Yes, target servers will be stopped after being created. If you select No, target servers will be started after being created.
   	Stop Source Server	If you select Yes, source servers will be stopped before incremental backups are created for them. This ensures data consistency as high as possible. If you select No, source servers remain running when incremental backups are created for them.
   Advanced Settings	Delete Intermediate Resources	If this function is enabled, intermediate resources generated during the migration, such as backups, snapshots, and images, will be deleted after the service cutover is complete.
   	Retain Primary NIC IP Addresses	If this function is enabled, the private and public IP addresses of the primary NIC on source servers will be retained on target servers, and random private IP addresses will be allocated to source servers. You need to manually roll back this operation if needed.

8. Configure the workflow and click Next: Confirm. After confirming that the configuration is correct, click Create. The migration workflow will be created and displayed in the workflow list.
   

   After a migration workflow is created, it switches to the Waiting status, and the migration has not started.

9. Click the workflow name to go to the details page. The steps are predefined standard steps in the template. You can or add a step to the workflow.
10. Click Run in the Operation column to start the migration.
    • You can view the migration progress on the Steps tab page. The workflow can continue only after you perform the manual steps contained.
    • On the Servers tab page, you can view the migration status of each server.