Next steps
This topic describes the operations you can perform after creating a migration job.
View migration reports
Migration reports provide detailed information about migration results, including lists of files that were successfully migrated, that failed to migrate, and that were skipped. Use migration reports to understand the execution status of a migration task.
Report file types
Based on task execution results, migration reports include the following three types: total migration file list, failed migration file list, and skipped migration file list.
Migration report file naming rules
uid@jobid@runtimeid_total_list_n: the total migration file list. Multiple files may be generated, where n is an integer starting from 0.
uid@jobid@runtimeid_failed_list_n: the failed migration file list. Multiple files may be generated, where n is an integer starting from 0.
uid@jobid@runtimeid_skipped_list_n: the skipped migration file list. Multiple files may be generated, where n is an integer starting from 0.
Report field descriptions
The fields in a migration report describe the properties of files (objects) during the migration from source to destination. The following table describes the fields.
Field name |
Description |
Source file name |
The name of the source file, URL-encoded. |
Destination file name |
The name of the destination file, URL-encoded. |
Source file size |
The size of the source file. |
Destination file size |
The size of the destination file. |
Source file MD5 |
The MD5 hash of the source file. This field is present only when the source returns an MD5 value. |
Destination file MD5 |
The MD5 hash of the destination file. |
Source file CRC64 |
The CRC64 hash of the source file. This field is present only when the source returns a CRC64 value. |
Destination file CRC64 |
The CRC64 hash of the destination 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 destination file. |
Source object version ID (versioned migration only) |
Used only in versioned migration to indicate the version ID of the source object. |
Destination object version ID (versioned migration only) |
Used only in versioned migration to indicate the version ID of the destination object. |
Migration start time |
The start time of the file migration. |
Migration end time |
The end time of the file migration. |
Migration status |
transferred: the file was successfully migrated; failed: the file migration failed; skipped: the file migration was skipped. |
Error reason |
The description of the error that occurred. |
Get migration reports
Log on to the Data Online Migration console.
-
In the migration task list, click Manage for the corresponding task to go to its details page.
If you selected Do not push reports when creating the task, go to the task details page > History and click Generate Migration Report. After the report is generated, click Download Migration Report to download it locally.
If you selected Push reports when creating the task, go to the task details page > History. After the report is generated, click Download Migration Report to download it locally.
NoteMigration reports generated before the data migration task is complete may contain incomplete content. To obtain a complete migration report, download it after the task is complete.
Migration reports are for your reference only. The final migration result is based on the actual files at the destination.
After being generated, migration reports are stored in the specified OSS bucket. Based on the task execution record, the folder path prefix 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
Description
bucket
The destination bucket.
prefix
The migration directory prefix specified in the destination data address.
uid
The Alibaba Cloud account ID.
jobid
The task ID. You can find it on the task details page > Details.
runtimeid
The task execution record ID. You can find it on the task details page > History.
-
In the OSS console, navigate to the destination bucket to find the migration report files. You can download these files and view the detailed file list. We recommend that you use ossbrowser or ossutil to view the files.
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:
|
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.
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
Log on to the Data Online Migration console.
In the top menu bar, select the region where the task is located.
In the navigation pane on the left, choose Data Online Migration > Migration Tasks.
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.
In the History section, find the task that you want to manage and click Retry Failed Files in the Operation column.
Modify the subtask name and click Next.
Confirm that parameters such as migration bandwidth, files migrated per second, and overwrite method are correct, and then click Next.
Click OK. The subtask starts and retries the migration of the failed files.