Keeping Private IP Addresses of Servers Unchanged After the Migration

Disclaimer

• Service availability risks

  This feature can ensure that the private IP addresses of source servers are retained on target servers. It does not guarantee your services can run properly on the target servers. You need to evaluate and assume the risks arising from using this feature.

• Rollback description

  Migration workflows cannot automatically roll back the IP addresses of target servers to their original ones. If any problems happen when you use this function, you can perform a rollback manually.

• IP address conflicts

  Since the source and target servers have the same private IP addresses, there may be IP address conflicts. This may result in service unavailability.

• Unknown risks

  There may be other unknow issues since the migration does not detect or scan source services.

• Customer responsibilities

  You need to fully test and prepare for the migration as well as check and solve possible problems after the migration is complete. You are advised to simulate the migration in a test environment to evaluate potential risks and formulate corresponding countermeasures.

Notes and Constraints

• Shutting downing target servers

  To retain source servers' private IP addresses on the paired target servers, the target servers must be stopped. If a target server is not stopped, the system will stop it automatically.

• Subnet requirements

  When you select a subnet in the target VPC, the subnet must be in the same network range as the source servers.

• Network interface requirements

  A target server can only have one network interface. Extended network interfaces are not allowed for target servers.

• Supported IP version

  Only IPv4 addresses can be retained.

Preparations

• Preparing a Huawei account

  Before using MgC, prepare a HUAWEI ID or an IAM user that can access MgC and obtain an AK/SK pair for the account or IAM user. For details about how to obtain an access key, see Preparations.

• Creating a migration project

  Create a migration project on the MgC console. For details, see Managing Migration Projects.

Procedure

1. Download and install Edge.

   Prepare a Windows server on the source intranet for installing Edge. For details about the server requirements and Edge installation method, see Installing Edge for Windows.

2. Connect Edge to MgC.

   Register an account for logging in to Edge and connect Edge to MgC. For details, see Connecting the Edge Device to MgC.

3. Add resource credentials.

   After the connection is successful, add the credentials of the source servers to be migrated to Edge. For details, see Adding Resource Credentials. Correctly configure Resource Type based on the source servers when you add their credentials.

4. Discover source servers.
   MgC provides three collection methods to meet your requirements in different scenarios. You can choose a method based on your source environment.

   Figure 1 Collection methods
   

   • If your source servers are on a cloud platform, such as Alibaba Cloud, Huawei Cloud, AWS, Tencent Cloud, Google Cloud, or Azure, you can collect the data about your servers over the Internet. You can also manually add the server data to MgC.
   • If your source servers are in an on-premises IDC, you can collect the server data over the intranet. MgC enables you to scan for servers by network range or VMware vCenter Server. You can also manually add the server data to MgC.

5. Group servers as an application.

   Group the discovered servers as an application to get sizing recommendations and execute the migration. For more information, see Grouping Resources as Applications.

6. Create an application assessment.

   The system will generate target server recommendations based on the collected source server details, including specifications, performance data, and workload types. For more information, see Getting Target Recommendations.

   After the target server recommendations are generated, you can:

   • Modify the recommended target configurations as needed. You can change the server and disk specifications. Disk downsizing is supported.
   • Associate source servers with target servers. If based on the target server recommendations, you find that you already have servers that match your requirements on Huawei Cloud, you can associate them with source servers.

7. Create a server migration workflow. After all the preceding steps are complete, go to the Workflows page and create a server migration workflow.
   

   • A workflow can contain a maximum of 100 servers.
   • You can migrate a maximum of 1,000 servers concurrently. For any servers beyond this number, the workflows will pause at the first step and put these servers in a pending state until other servers complete their migration. The workflows will then automatically start on these servers in the order the workflows were created.
   • If this is your first time to create a server migration workflow, you need to delegate MgC the required permissions. For more information about the required permissions, see Agency Permissions.
   1. In the navigation pane on the left, choose Migrate > Workflows. In the upper left corner of the page, select the migration project you created.
   2. Select the Server Migration template and click Configure Workflow.

      

   3. In the Workflow Details area, customize Name and Description.
   4. In the Application area, select the application you created in Step 5.
      

      For source servers in the selected applications, you need to get target server recommendations or associate them with target servers.

   5. In the Migration Network area, select a network type.
      • If you select Public, ensure that all target servers have EIPs bound. These EIPs will be used for the migration.
      • If you select Private, configure Direct Connect connections, VPN connections, VPC peering connections, or subnets in the target VPC in advance to ensure that the source environment can access the target environment.
   6. In the Target Environment area, select the VPC and subnet that have been connected to the source environment. The VPC and subnet will be used as the transit environment.
      

      The configured VPC and subnet will not be applied for the target servers associated with source servers. Parameters in Target Environment are not required if all source servers in the selected application are associated with target servers.

   7. In the Advanced Settings area, set Retain IP Address to Yes, read the on-screen warning and disclaimer, and click Confirm.
      

      Here only describes how to configure the Retain IP Address parameter. Set other parameters as required.

      

   8. From the VPC drop-down list, select the VPC that contains the private network segment of the source servers. From the Subnet drop-down list, select the subnet that contains the private IP addresses of the source servers. After you select a subnet, the system will check whether the selected subnet contains the source servers' private IP addresses. If it does not, you need to change the subnet.
   9. Click Next: Confirm.
   10. Confirm the workflow settings and click Confirm. The Run Workflow dialog box is displayed, which indicates that the workflow has been created.
       • If you want to start the migration immediately, click Confirm to run the workflow.
       • If you want to add a stage or step to the workflow, click Cancel. The workflow enters a Waiting state, and the migration has not started. To start the migration, click Run in the Operation column.
   11. On the migration workflow details page, view the workflow settings and the migration progress. After the step for starting the migration Agent is completed, a migration task is automatically created on the SMS console. For details about the server information mapping between MgC and SMS, see What Are the Information Mappings Between MgC and SMS?
       • Move the cursor to the migration progress bar. In the box that is displayed, view more migration details.
       • When the migration progress bar reaches a step that requires manual confirmation, move the cursor to the progress bar and click Confirm next to the step status in the displayed window, so that the subsequent migration steps can be executed.
       • When the workflow reaches the ResizeDiskPartition step, the system identifies whether disk capacity reduction has been performed on the target server.
         • If yes, go to SMS console and resize disks and partitions for the target server. For details, see the Partition Resizing parameter in Configuring a Target Server. After the adjustment is complete, go back to the MgC console and click Confirm next to the step status so that the workflow can continue.
         • If no, skip this step.
       • The StartSynchronization step is repeated before you verify your services on the target server.
       • When the progress bar reaches Cutover, the migration is complete. You need check whether your service systems are running properly on the target server. If they are, manually switch services to the target server. After the switchover is complete, click Confirm in the workflow. The system automatically performs the following steps SourceClear and MigrationTaskClear.

Manual Rollback

If you do not want to retain the private IP addresses of the source servers or any problems happen, you can manually switch the VPC for rollback. For details, see Changing a VPC.