All Products
Search

This Product

    Data Online Migration:What to do next

    Document Center

    Data Online Migration:What to do next

    Last Updated:Nov 18, 2025

    This topic describes the follow-up operations after you create a data migration task.

    View a migration report

    Migration reports provide detailed information about migration results, including lists of successful, failed, and skipped files. The reports help you understand the execution status of your migration task.

    Report file types

    Based on the task execution status, three types of migration report files are generated: a list of all migrated files, a list of failed files, and a list of skipped files.

    Migration report file naming convention

    • uid@jobid@runtimeid_total_list_n represents the list of all migrated files. There may be multiple files, where n is an integer greater than or equal to 0.

    • uid@jobid@runtimeid_failed_list_n represents the list of failed files. There may be multiple files, where n is an integer greater than or equal to 0.

    • uid@jobid@runtimeid_skipped_list_n represents the list of skipped files. There may be multiple files, where n is an integer greater than or equal to 0.

    Report field descriptions

    The fields in a migration report file describe various properties of a file (object) during its migration from the source to the destination. The fields include the following:

    Field name

    Description

    Source filename

    The URL-encoded name of the source file.

    Destination filename

    The URL-encoded name of the object file.

    Source file size

    The size of the source file.

    Destination file size

    The size of the object file.

    Source file MD5

    The MD5 hash of the source file. This field is present only if the source file returns an MD5 hash.

    Destination file MD5

    The MD5 hash of the object file.

    Source file CRC-64

    The CRC-64 hash of the source file. This field is present only if the source file returns a CRC-64 hash.

    Destination file CRC-64

    The CRC-64 hash of the object file.

    Source file last modified time

    The last modified time of the source file.

    Destination file last modified time

    The last modified time of the object file.

    Source object version ID (for multi-version migration only)

    This field is used only in multi-version migration to indicate the version ID of the source object.

    Destination object version ID (for multi-version migration only)

    This field is used only in multi-version migration to indicate the version ID of the destination object.

    Migration start time

    The time when the file migration started.

    Migration end time

    The time when the file migration ended.

    Abnormal migration (false: Normal, true: abnormal)

    A Boolean flag that indicates whether the migration was abnormal. `false` means normal and `true` means abnormal.

    Reason for abnormality

    A description of the reason for the abnormality.

    Get a migration report

    1. Log on to the Data Online Migration console.

    2. In the left navigation pane, choose Data Online Migration > Migration Tasks.

    3. In the migration task list, find the task that you want to manage and click Manage to go to its details page.

      • If you selected Do Not Push when you created the task, go to the task details page, click the History tab, and then click Generate Migration Report. After the report is generated, click Download Migration Report to download it to your local machine.

      • If you selected Push when you created the task, go to the task details page and click the History tab. After the report is generated, click Download Migration Report to download it to your local machine.

      Note

      • The generated migration report may be incomplete before the data migration task is complete. To obtain a complete report, download it after the task is finished.

      • The migration report is for reference only. The actual migrated content at the destination is the final version.

      After a migration report is generated, it is stored in the specified Object Storage Service (OSS) bucket. The prefix format of the folder directory level is based on the task execution status and is as follows:

      OSS://<bucket>/<prefix>/aliyun_import_report/<uid>/<jobid>/<runtimeid>/total_list/
OSS://<bucket>/<prefix>/aliyun_import_report/<uid>/<jobid>/<runtimeid>/failed_list/
OSS://<bucket>/<prefix>/aliyun_import_report/<uid>/<jobid>/<runtimeid>/skipped_list/

      Path parameter descriptions

      Field name

      Field meaning

      bucket

      The destination bucket.

      prefix

      The migration directory prefix specified for the destination data address.

      uid

      The ID of the Alibaba Cloud account.

      jobid

      The task ID. Get it from the task product page > Details tab.

      runtimeid

      The task execution record ID. Get it from the task product page > History tab.

    4. In the Object Storage Service (OSS) console, find the migration report files in the destination bucket. Download these files to view the detailed file lists. We recommend that you use the ossbrowser 2.0 (Preview) graphical management tool or the ossutil tool to view them.

    View migration logs

    Logs for the migration process can be pushed to SLS. These logs detail how each file is handled during the migration task, including records of successful, failed, and skipped files. Using migration logs, you can monitor migration progress in real-time, quickly locate problem files, and perform audits and troubleshooting.

    Log types

    Data Online Migration creates a project in SLS named aliyun-oss-import-log-Alibaba Cloud account ID-current console region, for example, aliyun-oss-import-log-137918634953****-cn-hangzhou. View the logs for the migration task in this project. The project contains the following two types of logs:

    • drs_import_success_log: Successful migration log

    • drs_import_fail_log: Failed migration log

    Log field descriptions

    The following table describes the main fields in the migration logs.

    Field name

    Field meaning

    JobName

    The name of the migration task.

    JobId

    The migration task ID.

    Region

    The region where the console is located.

    Status

    The status of the migrated file. It includes the following three statuses:

    • succeed: Successful

    • skipped: Skipped

      A migration can be skipped in the following two scenarios:

      • The source file does not exist when migration starts (it has been deleted).

      • The file is skipped based on the overwrite policy.

    • failed: Failed

    UserId

    The user's UID.

    ExecuteId

    The execution record ID.

    StartTime

    The migration start time.

    EndTime

    The migration end time.

    ListTime

    The time when the file was scanned.

    Time

    The current time.

    SrcObjectName

    The source file name. Fields starting with Src are related to the source.

    The filename is URL-encoded, for example, docs%2Fmy.docir%2Fexample.log.

    SrcObjectSize

    The source file size.

    DestObjectName

    The destination file name. Fields starting with Dest are related to the destination.

    The filename is URL-encoded, for example, docs%2Fmy.docir%2Fexample.log.

    DestObjectSize

    The destination file size.

    Get migration logs

    Push migration logs to Alibaba Cloud SLS in real-time for querying and analysis. In the SLS console, perform precise searches using keywords such as task ID and filename to monitor the migration process or troubleshoot issues.

    Important

    • The log push feature must be enabled when you create the migration task by selecting Push or Push only error logs. If you select Do not push when you create the task, you cannot view the task's logs in SLS.

    • Migration logs do not guarantee completeness. Do not use migration logs to verify migration integrity.

    • Migration logs are for your reference only. The final migration result is based on the actual files at the destination.

    • Do Not Push (default): Does not push migration logs.

    • Push: Pushes migration logs to SLS. View the migration logs in SLS.

    • Push Only File Error Logs: Pushes only error migration logs to SLS. View the error migration logs in SLS.

      Before you select Push or Push only file error logs, ensure that you have completed the following operations. Otherwise, the migration task may become abnormal:

      • You have activated the SLS service.

      • You have granted the required permissions for Simple Log Service Access Authorization on the authorization page.

    When you select Push or Push Only File Error Logs, Data Online Migration creates a project in SLS with a name in the format aliyun-oss-import-log-<Alibaba Cloud account ID>-<region>, for example, aliyun-oss-import-log-137918634953****-cn-hangzhou.

    • Simple Log Service Authorization: This option is displayed when you select Push or Push only file error logs for Migration logs.

      Click Grant. On the Cloud Resource Access Authorization page, the system creates the AliyunOSSImportSlsAuditRole role and grants it the required permissions. Click Agree To Authorization to complete the authorization.

    Retry failed files

    After a migration task ends, if the report shows that some files failed to migrate, create a new subtask to retry migrating only those failed files.

    Procedure

    1. Log on to the Data Online Migration console.

    2. In the top menu bar, select the region where the task is located.

    3. In the navigation pane on the left, choose Data Online Migration > Migration Tasks.

    4. In the migration task list, find the task that you want to manage and click Manage in the Actions column to go to its details page.

    5. In the History section, find the task that you want to manage and click Retry Failed Files in the Operation column.

    6. Modify the subtask name and click Next.

    7. Confirm that parameters such as migration bandwidth, files migrated per second, and overwrite method are correct, and then click Next.

    8. Click OK. The subtask starts and retries the migration of the failed files.