Scenario | Validation method used | Enable method | Description |
When retrieving data from the source, the source returns a CRC64 value. | CRC64 validation | No configuration is required in TOS; CRC64 validation is enabled by default. | After uploading an object to TOS, TOS calculates the CRC64 for the uploaded object, generates a CRC64 value, and returns it to DMS. DMS verifies the CRC64 value returned by the source and the CRC64 value returned by TOS to ensure data consistency between the source and destination. |
When retrieving source data, the source does not return a CRC64 value, and sampling verification is not enabled for DMS. | CRC64 validation | No configuration is required in TOS. CRC64 validation is enabled by default. | After DMS obtains an object, it calculates the object's CRC64 value. Once the object is uploaded to TOS, TOS also generates a CRC64 value for the object and returns it to DMS. DMS validates the CRC64 value generated by DMS against the CRC64 value returned by TOS to ensure the consistency of data between DMS and the destination. |
The source does not return the CRC64 value, but sampling verification is enabled in DMS. | Sampling verification tip If the source returns a CRC64 value and DMS enables the sampling verification feature, DMS will prioritize CRC64 verification. | You need to enable sampling verification when creating a migration task. For details, see Create Migration Task - Using Public Network. | DMS retrieves 100 bytes from each object on the source side and 100 corresponding bytes from the destination side, then validates them to ensure data consistency between the source and the destination. |