Help Center/ Migration Center/ User Guide/ Application Migration Projects/ Resource List/ Resource List Management
Updated on 2026-04-15 GMT+08:00
View PDF
Share

Resource List Management

Checking Discovered Source Resources

A discovery task can collect only basic information about source resources. More detailed information needs to be collected through a deep collection.
  1. On the Resource List page, check the resource list.
  2. Click a type to check the corresponding resources.
  3. Click a resource name to check its basic information.

Performing Online Deep Collection for Servers

This function collects detailed information about server specifications, NICs, and disk partitions. For details about the OSs that support deep collection, see OSs Supported for Collection and Migration.

Perform the following steps to perform a deep collection for your source servers:
  1. Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
  2. Locate a server in the resource list, then click Configure in the MgC Agent column. Configure the parameters based on Table 1.
    Table 1 Parameters for configuring a deep collection

    Parameter

    Configuration

    Type

    Set this parameter based on the OS type of the source server.

    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 pre-migration check is passed, the IP address you select here will be used for migration.

    Port

    Enter the accessible port of the source server.

    • 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 servers in batches, use the Change Port button above the list.

    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.

    NOTICE:

    The credentials you provide must have sufficient permissions, so the MgC Agent can collect necessary server details. Deep collection requires that the credentials you provide meet the following requirements:

    • Linux: root and its password
    • Windows: administrator and its password

    Whether to check migration items

    Decide whether to select the checkbox I authorize MgC to collect and save the raw data for later analysis. Selecting it helps identify risks beforehand.

    • Deselected: MgC only performs deep collection.
    • Selected: MgC performs deep collection and identifies dependency risks. Click a server name to check the analysis result on the resource details page.
  3. Click Confirm. The system automatically starts executing a deep collection. When Collected shows up in the Deep Collection column, the collection is complete.

Checking Servers Before Migration

Perform the following steps to check whether your source servers meet the migration requirements:
  1. Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
  2. Click Configure in the MgC Agent column.
  3. Configure the parameters based on Table 2.
    Table 2 Parameters for configuring a deep collection

    Parameter

    Configuration

    Type

    Set this parameter based on the OS type of the source server.

    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 pre-migration check is passed, the IP address you select here will be used for migration.

    Port

    Enter the accessible port of the source server.

    • 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 servers in batches, use the Change Port button above the list.

    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.

    NOTICE:

    The credentials you provide must have sufficient permissions, so the MgC Agent can collect necessary server details. Deep collection requires that the credentials you provide meet the following requirements:

    • Linux: root and its password
    • Windows: administrator and its password

    Whether to check migration items

    Decide whether to select the checkbox I authorize MgC to collect and save the raw data for later analysis. Selecting it helps identify risks beforehand.

    • Deselected: MgC only performs deep collection.
    • Selected: MgC performs deep collection and identifies dependency risks. Click a server name to check the analysis result on the resource details page.
  4. Click Confirm. The system checks whether the source server can be accessed using the information you provide and whether the server is ready to be migrated. If Completed shows up, the source server is ready.

Grouping Resources as Applications

This section describes how to group resources by application.

  1. Sign in to the MgC console. In the navigation pane, under Project, select your application migration project from the drop-down list.
  2. In the navigation pane, click Resource List.
  3. On the displayed page, select a type to check the corresponding resources.
  4. Select resources and click Group as Application above the list.
  5. Select an application from the drop-down list. If no applications are available, click Create Application in the displayed dialog box. Keep the default application name or enter a new one, enter a description, select a business scenario, environment, and region, and click Create.
  6. Click OK. The application name is now shown in the Application column of these resources.
Parent Topic: Resource List