How Does OMS Ensure Data Consistency Between the Source and Destination Buckets?

During the migration, whenever an object is migrated, OMS performs a consistency check on the object. If a source object is inconsistent with its corresponding destination one, the object is recorded as failed. OMS records all objects that fail to be migrated in the task. You can view the statistics in the task details.

If a source object does not meet any of the following criteria, the object fails the consistency check and is recorded as failed:

• After being uploaded to the destination bucket, the object has a same encryption attribute as the migration task. If the encryption attribute is different, handle this issue by referring to What Do I Do If a Migration Task Fails Due to an Inconsistent Encryption Attribute?
• The source object has the same size as its paired destination object.
• The last modification time of the source object is earlier than or equal to that of its paired destination object.