Migrating Servers from Alibaba Cloud to Huawei Cloud

1. Sign in to the MgC console from the Windows server you prepared in the source environment. In the navigation pane, under Project, select your application migration project from the drop-down list.
2. In the navigation pane, choose MgC Agent.
3. In the Application Migration (Manual Installation) area, choose Download > Download Windows Version to download the MgC Agent installation program to the Windows server.
4. Decompress the downloaded MgC Agent installation package and double-click the installation program to start the installation. If the installation program cannot be launched, try to run it in compatibility mode. For details, see How Do I Run the MgC Agent in Compatibility Mode? The default installation directory is C:\ and cannot be changed.
5. Click Finish to complete the installation and open the MgC Agent console.

MgC Agent supports three login methods. The following describes how to log in using the Huawei Cloud access key. For details about the other two login methods, see Login Using a Local Account and Login Using a Huawei Cloud ECS Agency.

1. On the login page, select Huawei Cloud Access Key.
2. Enter an AK/SK pair of your Huawei Cloud account, and select the region where you create migration projects on MgC from the drop-down list.
3. Click Privacy Policy, read the policy carefully, and select I have read and agree to the Privacy Policy.
4. Click Log In to access the Overview page of the MgC Agent console.

1. Sign in to the MgC Agent console.
2. On the Overview page, click Connect to MgC in the upper right corner.
3. In the Step 1: Select Connection Method area, select Huawei Cloud Access Key. Select the region where the project is created on MgC, enter an AK/SK pair of your Huawei Cloud account, and click List Migration Projects. After the MgC Agent is authenticated using the entered AK/SK pair, you can go to the next step. If the system displays a message indicating that the AK/SK pair is incorrect, try to rectify the fault by following the instructions in What Can I Do If the AK/SK Verification Fails?
   

   If your source servers need to be migrated, the entered AK/SK pair must have permissions to use SMS. For details, see SMS Custom Policies.

4. In Step 2: Select MgC Migration Project, select a migration project from the project drop-down list. The MgC Agent will report the collected information about your source resources to this project.
5. In Step 3: Preset MgC Agent Name, specify a name for the MgC Agent, which will be displayed on the MgC console, and click Connect. Confirm the connection to MgC, and click OK.
   

   After the MgC Agent is connected to MgC, the name you specified here cannot be modified.

6. If Connected shows up on the overview page, the connection to MgC is successful.

   

The following describes how to add credentials for each source server. This approach is recommended for a small number of servers. For large-scale environments, bind credentials during the migration readiness check.

1. In the navigation pane, choose Credentials.
2. Click Add Credential above the list.
   Figure 1 Adding a credential
   

3. Configure credential parameters based on Table 1.

   Table 1 Parameters for adding server credentials

   Parameter	Description
   Resource Type	Select Server.
   Type	Select the OS type of the server.
   Credential Name	Enter a custom credential name.
   Authentication Method	Select Username/Password.
   Username	Enter the username and password for logging in to the server. The credential you provided must have sufficient permissions, so the MgC Agent can collect necessary server details. The requirements for server credentials are as follows: Linux: root and its password Windows: administrator and its password
   Password
   IP Addresses	Set it to a single IP address or an IP address segment based on the source network configuration.

4. Set a credential validity period. The options for setting the validity period include:
   • Custom: Set the validity period of the credential, in days. The validity period starts when you click OK to save the credential. After this period ends, the credential becomes invalid. The default period is 60 days. You can specify an integer ranging from 1 to 365. If needed, you can extend the validity period for the credential when it is in the Unexpired, Expire soon, or Expired state.
   • Unlimited: The credential remains valid permanently. You can manually delete the credential when it is no longer needed.

5. Click OK to save the credential. If the MgC Agent is connected to MgC, the added credential will be automatically synchronized to MgC.

1. On the Select Source Resources page, select a platform from the Source Platform drop-down list.
   

   • The subsequent procedure depends on the source platform. Ensure that all servers included in the task come from the same platform.
   • If you want to collect server resources using SMS, set Source Platform to SMS Agent.

2. Click Add under Source Servers.
3. Select the source servers to be migrated and click Confirm.
   

   All servers in a migration task share the same settings (e.g., VPC, subnet, and security group). Verify your server selection before proceeding.

4. Click Next to access the Check Migration Readiness page.

1. Configure server credentials. There are two methods for you to do this.
   

   The credentials you provide must have sufficient permissions, so the MgC Agent can collect necessary server details. The requirements for server credentials are as follows:

   • Linux: root and its password
   • Windows: administrator and its password
   • Manual addition: You can choose this method if you configure credentials for a small number of servers. For more information, see Adding Resource Credentials.
   • Batch addition: You can choose this method if you configure credentials for a large number of servers.
     1. On the Check Migration Readiness page, click Associate Credentials above the list of servers to be migrated to download the template for configuring credentials in batches. Open the template file, enter the credential information (username and password) of all servers in the current migration plan, and save the file.

        

     2. Import the saved template file to the MgC Agent you connected to MgC. The system automatically configures the MgC Agent and credentials for the servers.

        

2. On the Check Migration Readiness page, in the list of servers to be migrated, click Configure in the MgC Agent column to configure an MgC Agent for each server.
3. Configure the parameters based on Table 3.

   Table 3 Parameters for configuring migration readiness check

   Parameter	Configuration
   OS Type	Set this parameter based on the source server OS type.
   MgC Agent	Select the MgC Agent installed in the source environment.
   Access IP Address	Select the IP address for accessing the source server. It can be a public or private IP address. After the migration readiness check is passed, the IP address you specify here will be used for migration.
   Access Port	Enter the accessible port of the source server. This port is used for deep collection and subsequent migration. The port defaults to 5985 for Windows. You can change it to any port that is accessible on the source server. The port defaults to 22 for Linux. You can change it to any port that is accessible on the source server. NOTE: To change the connection ports of source servers in batches, use the Change Port button above the list.
   Credential	Select the server credential added to the MgC Agent. If batch credential association is performed, the system automatically fills in the credential, and you do not need to select it.

4. Click Confirm. The system checks whether the source server can be accessed using the information you provide and whether the server can be migrated. If Completed shows up in the Migration Readiness Check column, the source server can be migrated.

   If the check fails, move the cursor to Check failed in the Migration Readiness Check column to view the failure cause. After rectifying the fault, click Check Again.

   

5. After all the source servers pass the readiness check, click Next to configure target servers.

There are two methods for configuring target servers.

• Associating source servers with target servers:

  If you have ECSs on Huawei Cloud, you can associate them with source servers for receiving migrated data.

  

  These ECSs should meet the following requirements:

  • It must be stopped. If the target server is running, stop it first.
  • It can be formatted. During the migration, the target server must be formatted, so it can receive data migrated from the source server.
  • It can access the Internet if you are migrating over the Internet.
  1. On the Configure Target page, select Associate existing target servers for Configuration Method.
  2. In the Target Region drop-down list, select the region where the existing target servers are located. For Project, the default IAM project in the selected region is used.
  3. Locate a source server and click Associate Target in the Operation column.
  4. Select the desired target server and click Confirm.
• Purchasing new target servers:

  The system automatically purchases target servers based on the configured specifications. However, if the source servers have dynamic disks, you need to purchase target Huawei Cloud ECSs in advance, and bind the source servers to the target servers.

  1. On the Configure Target page, select Purchase new target servers for Configuration Method.
  2. Select a method for configuring target servers.
     • Method 1: Generating target recommendations. You can choose to let the system recommend you right-sized Huawei Cloud servers based on the source server specifications. In the migration process, the system will automatically purchase target servers based on your settings.
       1. In the source server list, select the ones for which you want to generate target recommendations. Then click Generate Target Recommendations above the list.
       2. Configure an assessment policy based on Table 4.

          Table 4 Settings used for computing target recommendations

          Parameter	Description
          AZ	Select an AZ for your target server. The system will provide a recommendation based on your selection.
          Priority	High performance MgC recommends target resources designed for optimal performance. Low cost MgC recommends the most cost-effective target resources that meet your demands.
          Preferences	Configure your preferences for target servers. The system will prioritize your preferences and try to match them first during the recommendation process. For details about how the system recommends appropriate target resources, see How Does MgC Generate Target Server Recommendations? Server Types (Optional) Select the server types you prefer. Server Series (Optional) Select the server series you prefer. The system will generate recommendations based on your preferred server types and series. NOTICE: If you select Display only series allowed on DeHs, the server series allowed on DeHs in the target region will be listed, and Server Types will be dimmed. System Disk (Optional) Select the system disk type you prefer. Data Disk (Optional) Select the data disk type you prefer. Sizing Criteria Choose the criteria that the system will use to generate server recommendations. If the source servers are from the SMS Agent source platform, this function is not supported. If you select As-in on source, the system will recommend target servers with the same or similar CPU and memory capacities as the source servers. If you select Performance-based, you need to perform a performance collection for the source servers, and then set assessment parameters. The system will then recommend target servers with your desired CPU and memory capacity. NOTICE: The more performance data is collected, the more accurate the recommendations are. It is recommended that the server performance data be collected for at least seven days.

       3. Click Confirm. If Configured shows up in the Target Configuration column, the target recommendations are generated. You can check the recommended configurations in the next two columns.
     • Method 2: Defining target server specifications in batches. You can manually configure target server specifications. Before proceeding with this method, carefully assess any associated risks. It is also essential to ensure that the chosen specifications meet your system requirements and compatibility standards.
       1. In the source server list, select the servers for which you want to manually configure target server specifications. Then, click Configure Target above the list or click Configure Target in the Operation column of a specific server. The Configure Target page is displayed on the right pane.
       2. On the Target Specifications page, select the target AZ. Servers under the AZ will be displayed. Then, select the target server specifications as required.
       3. (Optional) Apply images instantly. The system disk size of the target server must be greater than the minimum disk size (minDisk) required by the image. To configure images and system disk specifications for multiple servers, you can use the function of applying images instantly to apply the same image and system disk specifications to selected servers. During batch configuration, the system automatically verifies whether each server meets the minimum disk size requirement. If a server does not meet the requirement, the system automatically adjusts the system disk size. Data disk settings remain unchanged. This operation requires manual review. You are responsible for assessing any associated risks. Before applying an image, ensure that it meets your system requirements and compatibility expectations.
          1. Click Apply. The Apply Image Instantly page is displayed.
          2. The system automatically sets the system disk size based on the value of minDisk. You can also manually adjust the size. After confirming that the system disk specifications of all servers meet the requirements, click Confirm to apply the current image to all selected servers instantly.
       4. In the Target Disks area, select a storage type and size for each target server disk.
       5. Click Confirm. Manual will appear in the Target Configuration column.
     • Method 3: Importing target server configurations. You can export the server records, configure target server flavors, disks, and images, and then import the records back. Some technical expertise is needed for this process.
       1. In the list of source servers, choose Export/Import Target Configuration > Export Target Configuration to download the server records as an Excel file to the local PC.
       2. Open the exported file. On the first sheet named servers, the blue columns (A to G) indicate the source server information, which does not need to be modified. The yellow columns (H to K) indicate the target server information, which needs to be configured.
       3. Configure the target server information (in columns H to K) according to Table 5.

          Table 5 Parameters in columns H to K

          Parameter	Configuration
          flavor	Specify a flavor for each target server. The second sheet flavors lists the flavors in S (general-purpose) and C (computing-plus) server series available in the target region. Choose a proper flavor and copy the flavor name to this cell. NOTE: If a source server has been assessed, the recommended flavor is included in the exported file. If a source server has not been assessed, its flavor field is empty.
          disks(name,osDisk,type,capacity;)	Enter the information about all disks. Separate multiple disks with semicolons (;). You must specify the name, function (system disk or not), type, and size for each disk. Separate these items with commas (,). Specify a disk size as a numeric value without a unit. The default unit is GiB. Example: /dev/sda,true,SAS,1024;/dev/sdb,false,SAS,2046 NOTE: If a source server has been assessed, the recommended disk specifications show up in the exported file. If a source server has not been assessed, the source disk specifications remain in this column, but the disk type changes to SAS by default.
          image_type	Enter an image type. The options are: public: public image private: private image shared: shared image
          image	Enter an image name. You can view all images available in the target region on the third sheet images.

       4. After configuring a target server for each source server, save the Excel file. Return to the MgC console. Choose Export/Import Target Configuration > Import Target Configuration above the list of source servers.
       5. In the displayed dialog box, click Access OBS.
       6. Select a bucket and upload the Excel file to the bucket.
       7. After the upload is successful, return to the MgC console. In the Import Target Configuration dialog box, select the file stored in the OBS bucket from the drop-down list.
       8. Click Confirm to import the target server configurations.
          

          • If the flavor field is empty in a row, this row will be ignored during the import.
          • If the disk or image field is left empty in a row, the source server's disk and image information is used during the import.
          • If the number in the disk field in a row is inconsistent with what the source server actually has, an error message is reported, indicating that the disk numbers are inconsistent.
          • If in a row, the disk type conflicts with the flavor, an error message will be reported, indicating that the disk type is incorrect.
  3. (Optional) Configure the target network. If the target network has access restrictions or requires a transit node for communication, you can use the target transit IP address and port configuration function to specify the transit IP address and SSH port range (22 to 65535). The configuration information will be integrated into the migration task through the dynamic parameter transfer mechanism to ensure network path reachability and migration task continuity during the migration.
     

     After a migration task is created, the transit IP address and SSH port cannot be changed.

     1. In the upper right corner of the source server list, enable Configure target network. After this function is enabled, the Transit IP Address and SSH Port columns are added to the list of source servers.
     2. In the Transit IP Address column, enter the IP address of the transit proxy server.
     3. In the SSH Port column, enter the migration port of the target server. It defaults to 22. If port 22 is occupied, you can use one from 22 to 65535.

        The functions of the port are as follows:

        • For Linux servers, this port is used to establish transmission channels and transmit data.
        • For Windows servers, this port is used to establish transmission channels.
  4. (Optional) Configure a DeH to receive applications and data migrated from source servers. After the binding, the target server will be automatically created on the DeH you bound during the migration.
     1. In the upper right corner of the source server list, enable Use DeH.
     2. Select the source servers and choose DeH Configuration > Associate DeH above the list.
     3. Select the target DeH to be associated from the drop-down list and click Confirm. Associated will show up in the DeH column. You can click Details to view the associated DeH.
  5. Configure a target environment based on Table 6.

     Table 6 Parameters for configuring a target environment

     Parameter	Configuration
     VPC	Select a VPC for the target servers from the drop-down list. For details about how to create a VPC, see Creating a VPC. If the source IP address is 192.168.X.X, you are advised to create a VPC and a subnet that both belong to network range 192.168.0.0/16. If the source IP address is 172.16.X.X, you are advised to create a VPC and a subnet that both belong to network range 172.16.0.0/12. If the source IP address is 10.X.X.X, you are advised to create a VPC and a subnet that both belong to network range 10.0.0.0/8.
     Subnet	The subnet has to be in the same network segment as the VPC.
     Security Group	The selected security group must: Allow inbound ports 8899, 8900, and 22 required for Windows migrations. Allow inbound port 22 required for Linux file-level migrations. CAUTION: For security purposes, you are advised to only allow traffic from the source servers on these ports. These ports must also be opened on the firewalls of target servers. For details about how to create a security group, see Creating a Security Group.
     Disk Encryption	If this option is not selected, the system and data disks of target servers created during the migration will remain unencrypted. If this option is selected, the system and data disks of target servers created during the migration will be automatically encrypted. NOTE: This setting applies to all target servers newly created in the migration task. Their disks will be encrypted using the same key. Once a disk is created, the encryption attribute of the disk cannot be modified. Keys can be shared with accounts, not IAM users. To enable disk encryption, you need to create an agency to authorize EVS to access KMS. If you have the right to grant the permissions, grant the KMS access permissions to EVS directly. Once the authorization succeeds, you no longer need to perform the authorization again. If you do not have the right to grant the permissions, contact a user with the Security Administrator permissions to grant you the right and then repeat the preceding operations. After the authorization is successful, configure the following parameters: Select an existing key. Only enabled keys generated using the AES_256 encryption algorithm are supported. Select a key from the drop-down list. You can select one of the following keys: Default keys: After the KMS access permissions have been granted to EVS, the system automatically creates a default key and names it evs/default. Custom keys: You can choose an existing key or create a new one. For details about how to create a key, see Creating a Key. Enter a key ID Enter the ID of a key shared from another user. Ensure that the key is in the target region. For details, see Creating a Grant.
     Enterprise Project	Select the enterprise project you want to migrate to. The enterprise project default is selected by default. For details about enterprise projects, see What Is Enterprise Project Management Service?
     Tags	You can add tags to the target servers automatically created by the system to facilitate resource management. Click Add Tag and enter a tag key and tag value. For details about tags and tag naming rules, see Tag Overview. To add the same tag to multiple servers or other types of resources, you can create a predefined tag on the TMS console and then select it for the servers or resources. This frees you from repeatedly entering tag keys and values. For details, see Creating Predefined Tags.

1. Configure migration settings based on Table 7.

   Table 7 Migration settings

   Area	Parameter	Description
   Migration Network	Public	If you select Public, ensure that all target servers have EIPs bound. These EIPs will be used for the migration.
   	Private	If you select Private, configure Direct Connect connections, VPN connections, VPC peering connections, or subnets in the target VPC in advance to connect the source environment to the target environment. If the source environment cannot access the Internet, enter the private IP address of the source proxy server and the port used by the proxy software. If the source proxy server cannot access the Internet, put the SMS-Agent installation package at a location where the source servers can access directly or over a proxy. You can download the SMS-Agent installation package from the SMS console.
   Source Settings	Install rsync on Source NOTE: If the source server is from the SMS Agent source platform, this function is not supported.	Linux migrations depend on rsync. If rsync is not installed on a source server, the server will fail to be migrated. If this option is not selected, rsync will not be installed on the source servers. If this option is selected, rsync will be automatically installed on the source servers. The installation can succeed only if the source servers: Have Internet access. If a proxy server is required, ensure that the proxy settings are correctly set in /etc/yum.conf (for CentOS and Red Hat) or /etc/apt/apt.conf (for Ubuntu). Have outbound ports 80 (HTTP) and 443 (HTTPS) enabled by the firewalls and security groups. Have accessible software sources. You are advised to configure a source based on your location. Cross-country access to the official source may experience high latency and packet loss, which may result in download failures. Have sufficient CPU, memory, and I/O resources to prevent latencies or interruptions during installation. NOTE: If the automatic installation fails, manual installation is required. For details, see rsync Not Installed on the Source Server.
   Target Settings	Start Target After Migration	If this option is not selected, the target servers will be stopped after the migration is complete. If this option is selected, the target servers will be started after the migration is complete.
   	Retain Private IP Address of Primary NIC	If this option is selected, the private IP addresses of the source servers will be retained on the target servers after the migration is complete. Enabling it may cause risks. You need to evaluate and take responsibility for any potential risks. For details, see How Do I Keep the Private IP Address of a Server Unchanged After the Migration?
   	Install ECS Password Reset Plug-in	If this option is selected, the system automatically installs the ECS password reset plug-in (CloudResetPwdAgent) on the target servers during the migration. With this plug-in, you can perform offline password reset for a running or stopped ECS. This operation does not depend on other services, and you do not need to enter the old password or log in to the ECS. For more information about the one-click password reset plug-in, see Scenarios of the One-Click Password Reset Plug-in. If the plug-in is not installed or becomes invalid after the migration, you need to reinstall it. For details, see Installing the One-Click Password Reset Plug-in on an Individual ECS.
   Consistency Verification	Verify Data Consistency	If this option is not selected, data consistency will not be verified after the full replication is complete. You can modify the verification policy after the incremental synchronization is complete. If this option is selected, the system will automatically verify data consistency after the full replication is complete. This is a quick verification, and only the file size and last modification time will be verified. You can modify the verification policy after the incremental synchronization is complete.
   Advanced Settings	Set Bandwidth Limit	If this option is not selected, the migration traffic is not limited. If this option is selected, you can limit the bandwidth that can be used for migration based on the source bandwidth and service requirements. CAUTION: Consider the migration scale to set an appropriate bandwidth limit. If too small a bandwidth is allocated to a task that includes 10 servers, migration tasks may preempt the limited bandwidth resource, and some servers may fail to be migrated.
   	Enable Quick Mode	Enable this option if incremental synchronization is not required. This option is disabled by default. If it is enabled, incremental synchronization is skipped and then subsequent steps are performed after full replication is complete in the migration task. Set this option based on your requirements.
   	Send SMN Notifications	Determine whether to get SMN notifications about the migration. You can configure Topic, Language, and Trigger Condition. Before enabling this function, create an SMN topic and subscribe to it. For details, see Publishing a Template Message. NOTE: You can only choose an SMN topic in the default IAM project of the region where you currently use MgC. To enable this function, you need to authorize MgC when the system prompts you. Select one or more trigger conditions. Migration succeeded: A notification will be sent if all resources in the migration task are migrated. Migration failed: A notification will be sent if any resource in the migration task fails to be migrated. Manual checkpoint: A notification will be sent if all resources in the migration task are waiting for manual confirmation.

2. Click Next to open the Confirm page.

1. On the Confirm page, check the resource and migration settings carefully to ensure that they meet your requirements. To update the settings, click Previous to return to the corresponding stage for modification.
2. In the Quota Verification area, the system will check whether the resource quotas in the target region meet the request. If no, increase the quota and verify again. Ensure that all check items meet the quota requirements.
3. On the Confirm page, verify that the resource and migration settings are correct and that all quotas meet the requirements. Then, click Finish. The Start Migration Task dialog box is displayed. The migration task has been created. Determine whether to start the migration immediately.
   • If you want to start the migration immediately, click Confirm to run the task.
   • If you want to save the migration settings without starting the migration, click Cancel. The task status will change to To be started. To run the task, click Run in the Operation column to manually start the migration.

4. (Optional) Add a phase or step.

   Adding checkpoints to migration tasks helps you control the migration process. For details, see Adding a Pre-/Post-Migration Stage and Step (Checkpoints and Scripts).