Help Center/ Migration Center/ Getting Started/ Quickly Migrating Servers in Batches
Updated on 2026-09-28 GMT+08:00

Quickly Migrating Servers in Batches

This section describes how to create a batch server migration task on MgC. MgC provides different types of migration tasks for various server migration scenarios. For details, see Server Migration Tasks.

Notes and Constraints

  • A migration task can only include source servers from the same platform.
  • A server can only be included in one migration task.
  • A migration task can include a maximum of 100 servers.
  • Source servers in tasks created by the same user must have unique MAC addresses. Duplicate MAC addresses may cause network conflicts or task execution errors.
  • You can migrate up to 200 resources at the same time. Any additional resources beyond this limit will have their migration paused at the initial step and stay in a pending state. Once resources are released or servers are migrated, these tasks will automatically resume in the order they were created.
  • If this is your first time creating a batch server migration task, assign the required permissions to your Huawei Cloud account. For more information about the required permissions, see Agency Permissions.

Precautions

Before creating a server migration workflow, read and understand the items below.

Item

Remarks

Source download bandwidth

Used to download the 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

Available CPUs and memory

  • Memory: at least 520 MB
  • CPU: at least 0.3 CPUs in Linux and 1 CPU in Windows

OS compatibility

For details, 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 costs that may be incurred during the migration, see Billing.

Permissions configuration

IAM is used for fine-grained permissions management. For details, 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?

Changes in server configurations before and after migration

For details about the configurations that may change after the migration, see What Are the Differences Between the Source and Target Servers After the Migration?

Migration Principles

Figure 1 shows the principles of server migration using MgC.
Figure 1 Server migration principles

Operation Process

Table 1 introduces the complete process of creating a batch server migration task.
Table 1 Batch server migration process

Step

Description

Preparations

Sign up for a Huawei Cloud account, complete real-name authentication, and obtain an AK/SK pair.

Step 1: Create an Application Migration Project

Create a project to separate and manage migration resources for different scenarios, to streamline organization management and resource allocation.

Step 2: Install the MgC Agent and Connect it to MgC

The MgC Agent is a tool used to discover resources and collect their details. It is also used for executing migration workflow tasks.

Step 3: Discover Source Servers

Discover source servers and collect their details.

Step 4: Create a Server Migration Task

Create a batch server migration task. At this step, you will create a task template for configuration later.

Step 5: Configure the Migration Task

Select source resources, check migration readiness, configure target servers, set parameters, and confirm settings.

Step 6: Track the Migration Task

Start the migration task and check the migration status, stages, and steps.

Preparations

Before using MgC, prepare a Huawei Cloud account or an IAM user that has permissions to access MgC. In addition, you need to enable Huawei Cloud services, complete real-name authentication, and obtain an access key.

  1. Sign up for a Huawei Cloud account and complete real-name authentication. If you have already signed up for a Huawei Cloud account and completed real-name authentication, skip this step.
    1. Visit Huawei Cloud and click Sign Up.
    2. Sign up for a Huawei Cloud account.
    3. (Optional) Complete real-name authentication. Real-name authentication is the process of submitting valid identity information (such as a passport or business license) for verification when you use cloud services offered in the Chinese mainland. There are individual real-name authentication and enterprise real-name authentication.

      According to relevant laws and regulations, unauthenticated accounts cannot purchase cloud services in the Chinese mainland and your account and rights may not be protected. For more information, see Real-Name Authentication Overview.

      To complete real-name authentication, refer to:
  2. Create an IAM user and grant permissions to the user. Skip this step if you use a Huawei Cloud account (administrator account).
    1. Create an IAM user. For details, see Creating an IAM User or Creating an IAM User (New Version).
    2. Create a custom policy and grant permissions to the IAM user. For details, see Using Roles or Policies to Assign Custom Permissions to IAM Users or Using Identity Policies to Assign Custom Permissions to IAM Users (New Version). For details about how to grant permissions, see Assigning Permissions to an IAM User or Assigning Permissions to an IAM User (New Version).
  3. Obtain an AK/SK pair for the account.

    The Agent uses the AK/SK of the target account for authentication when connecting to the MgC console. For details, see Creating an Access Key.

Step 1: Create an Application Migration Project

  1. Sign in to the MgC console.
  2. In the navigation pane on the left, choose Settings.
  3. Under Migration Projects, click Create Project.

    Figure 2 Creating a project

  4. In the Create Project dialog box, set Project Type to Application migration.

    The project type cannot be changed after the project is created.

    Figure 3 Setting the project type to application migration

  5. Enter a project name and click Create. After the project is created, you can view it in the project list.

Step 2: Install the MgC Agent and Connect it to MgC

  1. Install the MgC Agent on Windows. Log in to the MgC Agent console using a Huawei Cloud Access Key.
  2. Connect the MgC Agent to MgC.

Step 3: Discover Source Servers

MgC provides the following methods for you to do this work.
  • Online Discovery: This method is recommended if your source servers run on a cloud platform, such as Alibaba Cloud, Huawei Cloud, AWS, Tencent Cloud, Google Cloud, or Azure.
  • Intranet Discovery: This method is recommended if your source servers run in an on-premises or vCenter environment.
  • Manual Addition: This method can be used in all scenarios.

The following describes how to perform an online discovery.

  1. Sign in to the MgC console. In the navigation pane, under Project, choose your application migration project from the drop-down list.
  2. In the navigation pane, click Resource Survey.
  3. Under Online Discovery, click Cloud Discovery.

    Figure 4 Cloud discovery

  4. Configure the parameters based on Table 2 to create a discovery task.

    Table 2 Parameters for creating a cloud discovery task

    Area

    Parameter

    Description

    Task Settings

    Source Platform

    Select the source cloud platform. Currently, Alibaba Cloud, Huawei Cloud, AWS, Tencent Cloud, Google Cloud, and Azure are supported.

    Collection Method

    If you choose Credential, select the credential for accessing the source cloud platform. If the credential is not in the drop-down list, click Add Credential to add it. For details, see Managing Credentials.

    • If the source cloud platform is Alibaba Cloud, Huawei Cloud, AWS, or Tencent Cloud, select AK/SK for Authentication and enter the AK/SK pair of your source cloud account.
    • If the source cloud platform is Google Cloud, select Configuration File for Authentication and upload the configuration file that contains your Google Cloud service account credentials. The file must be in JSON format and cannot exceed 4 KB. For details about how to obtain the configuration file, see Obtaining Google Cloud Credentials Configuration Files.
    • If the source cloud platform is Azure, select ID/Secret for Authentication. To learn how to obtain Azure credentials, see How Do I Obtain Azure Credentials?

    If you choose Agency, a cloud service agency is required to assign MgC the permissions required to access resources in your current account. For details about the agency permissions, see Cloud Discovery.

    NOTE:

    This option is available only when Source Platform is set to Huawei Cloud.

    If the Agency Status is Agency not set up, click Create Agency. On the displayed page, click OK. After the authorization is complete, the agency status changes to Agency set up.

    Region

    Select the regions where your source resources are deployed.

    Resource Type

    Select Servers from the drop-down list.

    Basic Information

    Task Name

    The default name format is <task type>-<current-time>. You can also specify a name.

    Task Description (Optional)

    Describe the task.

    Application (Optional)

    Select the application that you want to group the discovered resources into. If no applications are available, perform the following steps to create one:

    1. Click Create Application. Enter an application name and description.
    2. Configure Business Scenario and Environment, and set Region to the region that you want to migrate to.
    3. Click OK.

  5. Click Confirm. After the online discovery task is created, MgC starts discovering source resources.

    • If the task succeeds, return to the Source Resources page and view the list of discovered source resources and their details.
    • If the task fails, click the task name to view the data source that fails to be collected. Hover over the collection status to view the failure cause.
      Figure 5 Viewing the failure cause

Step 4: Create a Server Migration Task

  1. In the navigation pane, choose Server Migration > Bulk Servers.
  2. Click Create Migration Task.
  3. Use the default task name or create one. Enter the task description (optional).
  4. Click OK to complete the task creation.

Step 5: Configure the Migration Task

This step includes five stages: Select Source Resources, Check the Migration Readiness, Configure Target Servers, Configure Migration Settings, and Confirm the Configurations. For details about the configuration at each stage, see Configuring a Migration Task.

Step 6: Track the Migration Task

In the migration task list, click the task name to go to the Task Details page. Check the task progress and perform the following operations on it.
Table 3 Operations related to resources

Scenario

Operation

Checking migration details

Click a resource name. On the Resource Details page displayed on the right, check the basic information, migration status, and migration progress.

Checking a target server

After the step CreateTargetServer is completed for a resource, choose More > View Target Resource in the Operation column to review details about the target server.

Checking an SMS task

After the step StartUpAgent is completed for a resource, a migration task is automatically created on the SMS console. To check the details on the SMS task, click View Migration Task in the Operation column.

Resizing disks and partitions

When the workflow on a resource reaches the ResizeDiskPartition step, the system identifies whether the target server's disk capacity has been reduced.
  • If yes, go to the SMS console and resize disks and partitions for the target server. For details, see the Resize Disks and Partitions parameter in Configuring a Target Server. After the adjustment is complete, return to the task details page and choose More > Confirm in the Operation column to continue the migration.
  • If no, choose More > Skip in the Operation column to skip this step and proceed with the subsequent migration steps.

Pausing a resource migration

You can pause the migration of a single resource in a migration task.

During the migration, when the resource reaches the full or incremental replication step, you can click Pause in the Operation column to pause the migration of the resource.

To resume the migration, click Run in the Operation column.

NOTICE:

After the migration of a resource is paused, do not perform any operations on the corresponding migration task on the SMS console.

Repeating incremental synchronization

The StartSynchronization step can be repeated. When a resource reaches the BusinessValidation step and the resource status is Not confirmed, select the resource and click Run Previous Step above the resource list. Alternatively, choose More > Run Previous Step in the Operation column of the resource to repeat incremental synchronization.

CAUTION:

You are not advised to perform incremental synchronization on the SMS console. Otherwise, the migration task status on the MgC console may differ from that on the SMS console, causing abnormal task running.

Verifying services

When the workflow on a resource reaches the BusinessValidation step and there is no more incremental synchronization, verify services on the target server. After services pass the verification, click Confirm in the Operation column of the corresponding resource to enter the Complete cutover stage.

Switching traffic

The workflow moving to the Cutover step means that the target server has been verified and you can transfer services to the target server. After the switchover is complete, return to the task details page and click Confirm in the Operation column. The system automatically performs the subsequent SourceClear and MigrationTaskClear steps.