Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Migration Center/ Best Practices/ Server Migration/ Migrating On-premises Servers to Huawei Cloud

Migrating On-premises Servers to Huawei Cloud

Updated on 2025-02-17 GMT+08:00

Scenario

This section describes how to use MgC to migrate on-premises servers to Huawei Cloud.

Preparations

  • Prepare a Windows server for installing the MgC Agent (formerly Edge) in the source intranet environment. The Windows server must:
    • Be able to access the Internet and the domain names of MgC, IoTDA, and other cloud services. For details about the domain names to be accessed, see Domain Names.
    • Allow the ports required by the MgC Agent (formerly Edge). For details about the required ports, see Communication Matrix.
    • Use PowerShell 3.0 or later.
    • Have at least 4 CPUs and 8 GB of memory.
    • Allow outbound traffic on 8883 if the server is in a security group.
    • Not have any antivirus or protection software enabled. This type of software may stop the MgC Agent from executing migration commands, resulting in migration failures.
    CAUTION:

    Do not install the MgC Agent on a source server to be migrated.

    • High resource consumption: The MgC Agent consumes CPU and memory resources during collection and migration. If a large number of migration tasks are performed by the MgC Agent, services on the source server may be affected.
    • Port occupation: The MgC Agent occupies some ports on the server, which may affect services running on it.
  • If there are Windows source servers to be migrated, these servers must:
    • Allow access from the server where the MgC Agent is installed over port 5985.
    • Have WinRM enabled and have connected to the server where the MgC Agent is installed. For more information, see How Do I Configure WinRM on a Windows Source Server and Troubleshoot WinRM Connection Problems?
    • Allow the execution of shell scripts. Open PowerShell on the source servers as an administrator and run the following command to view the current execution policy:
      Get-ExecutionPolicy
      If Restricted is returned, no script can be executed. Run the following command and enter Y to change the policy to RemoteSigned:
      Set-ExecutionPolicy RemoteSigned
  • If there are Linux source servers to be migrated, these servers must:
    • Allow access from the server where the MgC Agent is installed over port 22.
    • Allow direct root access. That means remote connections using root with SSH or other tools must be allowed on these Linux source servers.
    • Have SFTP and SSH enabled.
    • Support the following SSH connection security algorithms:

      ssh-ed25519, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521, rsa-sha2-512, and rsa-sha2-256

      If a server does not support the preceding security algorithms, you are advised to upgrade OpenSSH to 8.0 or later. Otherwise, deep collection cannot be performed for that server.

    • Have their iptables configured to allow all communications with the server where the MgC Agent is installed. Run the following command on the source servers. If the source field in the command output contains the IP address and port of the server where the MgC Agent is installed, it means that the MgC Agent is not allowed to access these source servers. In this case, ensure that access from the MgC Agent is permitted
      iptables -L INPUT -v -n

  • Prepare a Huawei account or an IAM user that can access MgC. For details, see Preparations.
  • Create a migration project on the MgC console.

Notes

Before creating a server migration workflow, read and understand the following precautions.

Item

Precaution

Source download bandwidth

Used to download SMS-Agent to source servers.

  • If each source server uses a dedicated bandwidth, the bandwidth must be at least 30 Mbit/s.
  • If source servers share a bandwidth, the average bandwidth must be at least 50 Mbit/s.

Migration bandwidth

  • Used to migrate data. It affects the migration speed and duration.
  • For details about how to estimate the migration duration, see How Long Does a Migration Take?

CPU and memory

  • At least 520 MB of available memory
  • At least 0.3 CPUs available in Linux and at least 1 CPU available in Windows

OS compatibility

For details about what OSs are supported, see Supported OSs.

Server migration statements

For details about the important statements you need to understand before the migration, see What Are the Important Statements of SMS?

Notes and constraints

For details about the notes and constraints for server migration, see Notes and Constraints.

Billing

For details about the fees that may be incurred during the migration, see Billing.

Permissions configuration

For details about the permissions the target account must have, see Permissions Management.

Migration network and ports

For details about the requirements for the migration network and ports, see How Do I Set Up a Secure Migration Network for Using SMS?

Step 1: Download and Install the MgC Agent (Formerly Edge)

Install the MgC Agent and connect it to MgC. For more information, see Installing the MgC Agent.

Step 2: Add Servers to MgC

  1. Sign in to the MgC console. In the navigation pane, under Project, select an application migration project from the drop-down list.
  2. In the navigation pane, choose Discover > Source Resources.
  3. On the Servers tab, click Add above the list.

    Figure 1 Adding a server

  4. In the displayed dialog box, configure parameters listed in Table 1 and click Confirm. The system automatically checks the credential status and starts collecting resource details.

    Table 1 Parameters for adding a server

    Parameter

    Description

    Name

    Enter a server name.

    MgC Agent

    Select the MgC Agent installed in the source environment.

    Type

    Select the OS type of the source server.

    Access IP Address

    Enter the IP address of the source server.

    If the source server is in the same VPC as the MgC Agent, you can enter the private IP address of the server. Otherwise, you have to enter its public IP address.

    Port

    Enter the port on the source server that allows access from the MgC Agent.

    • By default, port 5985 on Windows source servers must be opened to the MgC Agent. The port cannot be changed.
    • By default, port 22 on Linux source servers must be opened to the MgC Agent. You can specify a different port if needed.

    Credential

    Select the server credential. If the credential is not displayed in the list, go to the MgC Agent console, add the server credential, and synchronize it to MgC.

  5. After the server is added, view it in the list.

Step 3: Group Servers as an Application

You can group the added servers as an application to get sizing recommendations for target resources and execute the migration.

  1. On the Resources page, in the Servers list, select the servers to be grouped as an application and click Group as Application above the list.
  2. Select an application from the drop-down list. If no applications are available, click Create Application. In the displayed dialog box, enter an application name and description; select a business scenario, environment, and target region; and click Create. For more information, see Creating an Application.
  3. Click OK. You can view the application name in the Application column of these servers.

(Optional) Step 4: Associate Source Servers with Existing Servers on Huawei Cloud

If you have servers on Huawei Cloud, you can associate source servers with these existing Huawei Cloud servers. These Huawei Cloud servers will be used to receive data migrated from their paired source servers. Then you can skip step 5 and go to Step 6: Create a Migration Workflow.

If you do not want to migrate data to these existing Huawei Cloud servers, skip the current step and go to Step 5: Create an Application Assessment.

CAUTION:

Before associating an existing server on Huawei Cloud with a source server, make sure that the existing server meets the following requirements:

  • Disks on the existing server can be formatted. During the migration, disks on the existing server will be formatted and re-partitioned based on the source disk settings for receiving data migrated from the source server.
  • To migrate over the Internet, the existing server must be able to access the Internet.
  • The existing server must be in the same region as the application that the source server is added to.
  1. In the navigation pane on the left, choose Design > Migration Solutions.
  2. Click View Resources in the Target Configuration card.
  3. On the displayed Servers tab, locate a source server and click Associate in the Target Association column.
  4. In the displayed dialog box, select the region of the application and select a project. Then, select an existing Huawei Cloud server and click Confirm.

    After the association is complete, Associated is displayed in the Target Association column. You can click Details to view the specifications of the associated target server.

Step 5: Create an Application Assessment

Assessing an application can get recommendations for most suitable Huawei Cloud resources based on the specifications, performance, and business purpose data of the source resources added to the application, as well as your selected recommendation references, such as, cost or performance reference and ECS type references.

NOTE:

If your source servers have been associated with existing servers on Huawei Cloud, you can skip this step and create a migration workflow to migrate them.

  1. On the Migration Solutions page, click Assess in the Target Configuration card.
  2. In the Select Application drop-down list, select the application that contains the source servers to be assessed.
  3. In the Select Resources area, select the servers to be assessed.
  4. Configure an assessment policy based on Table 2.

    Table 2 Settings used for computing target recommendations

    Parameter

    Option

    Description

    Target Region

    -

    Select the region where you want to purchase resources on Huawei Cloud. You are advised to select a region close to your target users for lower network latency and quick access.

    Assessment Policy

    Match source configuration

    MgC will recommend Huawei Cloud resources in the same or similar size as source resources.

    For details about how MgC recommends appropriate target resources for you, see How Does MgC Generate Target Recommendations?

    Match business scenario

    MgC recommends appropriate Huawei Cloud resources based on the business scenario of source resources and Huawei Cloud best practices.

    For details about how MgC recommends appropriate target resources for you, see How Does MgC Generate Target Recommendations?

    Priority

    High performance

    MgC recommends target resources with optimal performance.

    Low cost

    MgC recommends the most cost-effective target resources that meet your demands.

    Preferences

    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, Server Types will be dimmed, and the server series allowed on DeHs in the target region will be listed.

    System Disk (Optional)

    Select the system disk type you prefer.

    Data Disk (Optional)

    Select the data disk type you prefer.

    Sizing Criteria

    Select the criteria that the system will follow for generating server recommendations.

    For details about how MgC recommends appropriate target resources for you, see How Does MgC Generate Target Recommendations?

  5. Click OK.
  6. In the application list on the Migration Solutions page, locate the applications and click View Target Configurations in the Operation column.

    In the Target Configurations area, you can view the specifications of Huawei Cloud resources recommended based on the source resource specifications and your preferences. It also gives you the ability to estimate the cost of running on Huawei Cloud. In addition, you can modify the recommended target configurations.

Step 6: Create a Migration Workflow

Create a workflow to migrate the source servers to Huawei Cloud. For details, see Creating a Server Migration Workflow.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback