Updated on 2026-10-27 GMT+08:00

Creating a File Storage Migration Task

This section describes how to create a file storage migration task and configure parameters.

Prerequisites

Step 1: Create and Configure a File Storage Migration Task

  1. Sign in to the MgC console. In the navigation pane, select the created application migration project from the drop-down list.
  2. In the navigation pane on the left, choose Storage Migration > File Storage.
  3. Click Create Migration Task.
  4. Set workflow basics based on Table 1.

    Table 1 Basic parameters

    Parameter

    Description

    Name

    User-defined. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. The name must start with a letter or digit, and it must not start or end with a period.

    Region

    Select the region you are migrating to.

    Description

    User-defined. It can contain a maximum of 255 characters. Allowed characters include letters, digits, hyphens (-), underscores (_), commas (,), periods (.), spaces, and decimal points (.). It cannot start with a decimal point (.), hyphen (-), or underscore (_).

    Cluster

    Select the migration cluster created in Creating a Migration Cluster.

  5. Configure the migration source and target based on Table 2 and Table 3.

    Table 2 Parameters for configuring a migration source

    Parameter

    Description

    Remarks

    Location Type

    Select a location type as required. NAS_NFS_V3_PROTOCOL (file systems using the standard NFSv3 protocol) is recommended for better listing performance.

    -

    File System Address

    Enter the mount address of the source file system. The format is IP address:/ or IP address:/xxx, for example, 192.1.1.1:/0001.

    -

    Path

    Enter the directory that contains the files to be migrated. The format is /<folder-name>.

    If you enter /, the entire source file system will be migrated.

    Table 3 Parameters for configuring a migration target

    Parameter

    Description

    Remarks

    Location Type

    Select NAS_NFS_V3_MOUNT (non-standard NFSv3 file system).

    -

    File System Address

    Enter the mount address of the target file system. To obtain the mount address, go to the file system list and click the icon next to the address in the Mount Point column.

    -

    Path

    Enter the directory for storing migrated files. The format is /<folder-name>.

    If you enter /, source files will be migrated to the root directory of the target file system.

  6. Configure migration settings based on Table 4.

    Table 4 Migration settings

    Parameter

    Sub-parameter

    Description

    Migration Method

    Full migration

    This method enables migration of all data in a source bucket or folder.

    List migration

    This method enables the migration of specific files and folders recorded in predefined lists.

    In List Path box, enter the path of the object lists stored in the target bucket. Restrictions on an object list file vary with the target location.

    • Target location: Huawei Cloud OBS
      • An object list file cannot exceed 30 MB.
      • An object list file must be a .txt file, and the Content-Type metadata must be text/plain.
      • An object list file must be in UTF-8 without BOM.
      • Each line in an object list file can contain only one object name, and the object name must be URL encoded.
      • Each line in an object list file cannot exceed 16 KB, or the migration will fail.
      • The ContentEncoding metadata of an object list file must be left empty, or the migration will fail.
      • An object list file can contain a maximum of 10,000 lines.
    • Target location: NAS
      • An object list file cannot exceed 30 MB.
      • An object list file must be a .txt file.
      • An object list file must be in UTF-8 without BOM.
      • Each line in an object list file can contain only one object name, and the object name must be URL encoded.
      • Each line in an object list file cannot exceed 16 KB, or the migration will fail.
      • An object list file can contain a maximum of 10,000 lines.
    CAUTION:

    Prefix migration

    This option is only available for cloud storage migration.

    If you enter a file name or name prefix in the Prefix box, only the objects that exactly match the specified name or prefix are migrated.

    • If the files to be migrated are stored in the root directory of the source bucket, add their name prefixes directly. If the files are stored in a non-root directory, add their path prefixes in the format of <folder-name>/<prefix>.
    • Use commas (,) to separate multiple prefixes.

    Concurrent Subtasks

    -

    The default value is 5, but the value can be changed. There cannot be more than 10 concurrent subtasks for each online migration node. For example, if there are 2 online migration nodes, there can be up to 20 subtasks.

    Overwrite Existing

    Never

    Files existing at the target will never be overwritten.

    WARNING:
    • If you choose Never for the initial migration, the attributes of involved parent folders at the source will not be migrated to the target. As a result, the folder attributes may be incomplete at the target. This could impact data integrity, so use the Never option with caution.
    • If you choose Never, restarting a migration after an interruption or pause may lead to incomplete data migration, even though the task may appear successful. This could impact data integrity, so use the Never option with caution.

    Always

    Files existing at the target will always be overwritten.

    If older or different size

    • The system replaces existing target files if they are older than or differ in size from their source counterparts. Files with matching modification times and sizes remain unchanged and are skipped during migration.
    • The system verifies folders after their content is migrated. Folders that already exist at the target will be overwritten if they have different last modification times, sizes, or permissions from the paired folders at the source.
      NOTE:

      The same overwriting policy is applied to empty folders as to files.

    If different CRC 64 checksum

    If a source object has a CRC64 checksum different from the paired target object, the source object will overwrite the target one. Otherwise, the source object will be skipped during the migration. If either of them does not have a CRC64 checksum, their sizes and last modification times are checked.
    NOTE:
    • This option is only available for migration within Huawei Cloud or from Alibaba Cloud or Tencent Cloud.
    • Using this option requires that target OBS buckets be whitelisted for the CRC64 feature.

    Consistency Verification

    Size and last modified

    With this default method, the system checks data consistency by comparing object size and last modification time.

    NOTE:

    If the content of a file changes during migration but the file size and last modification time remain unchanged, the content of the migrated file may be inconsistent with that on the source.

    CRC64 checksum

    The system checks data consistency by comparing the CRC64 values in the metadata of source and target objects. If a source object or the paired target object does not have a CRC64 checksum, the OMS-calculated CRC64 value is used for verification. CRC64 verification may generate extra public traffic and request costs. For details, see Consistency Verification.
    NOTE:
    • NAS_NFS_V3_MOUNT and NAS_NFS_V3_PROTOCOL are supported.
    • Using this option requires that target OBS buckets be whitelisted for the CRC64 feature.

    Migrate Metadata

    -

    Determine whether to migrate metadata.

    • If you select this option, object metadata will be migrated.
    • If you do not select this option, only the Content-Type and Content-Encoding metadata will be migrated. If the source storage service provider does not provide the metadata (for example, UCloud does not provide Content-Encoding), the metadata will not be migrated.

    Clear Cluster

    -

    Determine whether to clear the migration cluster after the migration is complete.

    • If you select this option, a step for clearing the migration cluster will be created in the workflow. You can also choose whether to clear resources used by the cluster, such as NAT gateways, security groups, and VPCEP resources.
    • If you do not select this option, a step for clearing the migration cluster will not be created in the workflow, but the migration cluster and its resources will automatically be deleted 30 days after the workflow is created.

  7. (Optional) Configure advanced options based on Table 5.

    Table 5 Advanced options

    Parameter

    Description

    Filter Source Data

    Use exclude patterns, include patterns, and time ranges to filter files to be migrated. For details about filters, see Source Data Filters.

    Send SMN Notifications

    Determine whether to use SMN to get notifications about migration results.

    • If you do not select this option, no SMN messages will be sent after the migration is complete.
    • If you select this option, after the migration is complete, SMN messages will be sent to the subscribers of the selected topic. You can select the language and trigger conditions for sending messages.

    Limit Traffic

    Set the maximum bandwidth to be used by the migration workflow during different periods.

    • If you do not select this option, migration traffic will not be limited.
    • If you select this option, you can limit the migration traffic by setting Start Time, End Time, and Bandwidth Limit.
      For example, if you set Start Time to 08:00, End Time to 12:00, and Bandwidth Limit to 20 MB/s, the maximum migration speed is limited to 20 MB/s from 08:00 to 12:00. The migration speed is not limited outside this period.
      NOTE:
      • The bandwidth limit ranges from 1 MB/s to 1,048,576 MB/s.
      • A maximum of five rules can be added.
      • The time is the local standard time of the region you are migrating to.

    Schedule Migration

    Schedule the migration to run during a period.

    • If you do not select this option, you need to manually start or stop the migration.
    • If you select this option, the migration runs during the specified period and stops outside that period.

      For example:

      • If you set Start Time to 08:00 and End Time to 12:00, the migration task runs from 08:00 to 12:00 every day. The migration stops outside that period.
      • If you set Start Time to 12:00 and End Time to 08:00, the migration runs from 12:00 of the current day to 08:00 of the next day. The migration stops outside that period.

Step 2: Confirm the Configuration

  1. After the migration task is configured, click Next to confirm the information.
  2. Confirm the settings and click Confirm. The Start Migration Task dialog box is displayed, indicating that the workflow has been created.

    • If you want to start the migration immediately, click Confirm to run the workflow.
    • If you only want to save the settings and start the migration later, click Cancel. The status of migration tasks becomes Waiting, and the migration has not started. You can click Start in the task list to start the migration.

Step 3: 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.
  • Checking the resource status: Click a resource name. On the Resource Details page displayed on the right, you can review the basic information, migration status, and migration progress of the resource. You can also perform the operations below.

    Operation

    Step

    Replacing the migration cluster

    You can replace the migration cluster only when the migration task (workflow) is Paused. Only healthy clusters can be used.

    1. In the Basic Information area, click Replace next to the migration cluster name.
    2. In the displayed dialog box, select a new cluster from the drop-down list and click Confirm. After the cluster is replaced, the workflow starts to run automatically.

    Modifying the migration schedule

    1. In the Basic Information area, click Modify under Schedule Migration.
    2. Set Start Time and End Time, and click Confirm.

    Modifying the number of concurrent subtasks

    1. In the Migration Progress area, click Modify above Expected Concurrent Subtasks to change the expected number of concurrent subtasks. There cannot be more than 10 concurrent subtasks for each online migration node. For example, if there are 2 online migration nodes, there can be up to 20 subtasks.
    2. Click Confirm.

    Adding traffic limiting rules

    1. In the Migration Speed area, click Add to add a rule to limit the bandwidth the migration can use in a specified period.
      NOTE:
      • The bandwidth limit ranges from 1 MB/s to 1,048,576 MB/s.
      • Time periods in different rules cannot overlap.

        For example, if there is a rule configured for the period from 8:00 to 12:00, you cannot configure rules for any overlapping periods, such as from 7:00 to 13:00, 7:00 to 8:00, and 9:00 to 12:00.

      • Start and end times must be on the same day, with the start time preceding the end time.

        For example, the time period from 23:00 to 01:00 of the next day is not allowed.

      • A maximum of five rules can be added.
      • The time is the local standard time of the region you are migrating to.
    2. Click Save.

    Obtaining the lists of migrated, skipped, or failed files

    In the Migration Statistics area, view the paths of the lists of migrated, skipped, or failed files, and the causes of failed objects. Click a file path, and it will take you to the OBS bucket where the list is stored. You can download the list from the bucket. You can locate the causes and rectify the faults by referring to Error Codes Returned for Failed Objects.

    Viewing traffic statistics

    In the Traffic Statistics area, view the migration traffic in the last 1 hour, last 6 hours, last 24 hours, or the entire migration period.

  • Confirming steps: Some resources require manual confirmation. In this case, click Confirm in the Migration Status column or in the Operation column to continue the migration.