Help Center/ Migration Center/ FAQs/ Storage Migration/ What Do I Do If the Storage Migration Workflow Fails and "COMPARISON_ATTRIBUTE_NOT_SAME" Is Displayed?
Updated on 2024-12-20 GMT+08:00
View PDF
Share

What Do I Do If the Storage Migration Workflow Fails and "COMPARISON_ATTRIBUTE_NOT_SAME" Is Displayed?

Symptom

The migration workflow failed, and the error message "COMPARISON_ATTRIBUTE_NOT_SAME" was displayed.

Solution

This issue is caused by a failed metadata verification. There are two cases:

  • Case 1: The mtime attribute in the metadata holds different meanings in the source and target storage systems. This happens if metadata migration is enabled for the migration from an object storage system to a PFS bucket. In the source storage system, mtime is a custom metadata attribute, while in the PFS bucket, this attribute represents the last modification time of a file. Even if the file can be migrated successfully, the error message indicating a metadata comparison failure will still appear. You can check whether the file has been successfully migrated to the target.
  • Case 2: The metadata mismatches between the source and the target. In this case, perform the migration again. If the fault persists, contact technical support or submit a service ticket.
Parent topic: Storage Migration