Updated on 2024-02-04 GMT+08:00

Monitoring a Synchronization Task

Scenarios

After a synchronization task is started, you can view the synchronization progress and details at any time.

Procedure

  1. Log in to the management console and go to the Object Storage Migration Service page.
  2. In the navigation pane on the left, choose Synchronization Tasks.
  3. Click on the left of the task ID and view the task progress. For details about the parameters, see Table 1.

    Figure 1 Monitoring a synchronization task
    Table 1 Monitoring data of a synchronization task

    Parameter

    Description

    Requested Objects (Last 30 days)

    Number of objects covered by the synchronization requests received from the source platform this month.

    Objects (Last 30 days)

    • Synchronized

      Number of objects that have been synchronized this month. You can view the synchronized objects in the synchronized object list stored in the destination bucket.

    • Failed

      Number of objects that failed to be synchronized this month. You can view the failed objects in the failed object list stored in the destination bucket.

    • Ignored

      Number of objects that have been ignored this month. You can view the ignored objects in the ignored object list stored in the destination bucket.

      NOTE:

      If an object with the same name and size exists in the destination bucket, and its last modification time is later than that in the source bucket, the source object will be ignored during synchronization.

    Synchronized Object Size (Last 30 days)

    Total size of objects that have been synchronized in the past 30 days.

    Object Lists

    OMS records the successfully synchronized objects, objects that failed to be synchronized, and ignored objects in three separate lists and stores these lists in the destination bucket. You can use these lists to verify the numbers and names of the synchronized, failed, and ignored objects. For details, see Table 2.

    Synchronization API URL

    Specifies the address for receiving synchronization requests from the source platform. These requests will trigger data synchronizations. For details about the OMS synchronization API, see Creating a Synchronization Event.

    Table 2 Object lists

    Object Type

    Directory

    List Content

    Synchronized objects

    oms/sync_task/Synchronization task ID/success_object_lists

    Occurrence time (in local UTC), non-URL-encoded names of synchronized objects, and object sizes (in bytes)

    Failed objects

    • oms/sync_task/Synchronization task ID/failed_object_lists
      For example, oms/sync_task/Synchronization task ID/failed_object_lists/oms-task-sync-test-20210107111623197_596
      NOTE:

      This directory stores the list of objects that failed to be synchronized during the migration.

    • oms/sync_task/Synchronization task ID/failed_object_lists/creation_failures
      For example, oms/sync_task/Synchronization task ID/failed_object_lists/creation_failures/1609833838031_5ff41d6e85e877149d44bb55_4.failed_list.txt
      NOTE:

      This directory stores the list of objects that fail to be migrated due to task creation failures. If the account is in arrears, frozen, or does not have the required permissions, the task creation will fail.

    Failure causes, occurrence time (in local UTC), URL-encoded and non-URL-encoded names of failed objects, and error codes returned by source SDKs

    Ignored objects

    oms/sync_task/Synchronization task ID/skip_object_lists

    Occurrence time (in local UTC), non-URL-encoded names of ignored objects, and object sizes (in bytes)

    Objects to be synchronized

    oms/sync_task/Synchronization task ID/object_lists

    Named of objects to be synchronized

    NOTE:

    OMS automatically records the names of objects to be synchronized covered by the received synchronization requests in .txt files, and stores the files in the oms/sync_task/Synchronization task ID/object_lists directory of the destination bucket.

    The statistics displayed on the synchronization task details page are delayed for about 1 hour and for reference only.