Data Integrity Checking TntDrive can calculate checksums for files uploaded to Amazon S3 or S3-compatible storage and verify checksums when files are downloaded back. This helps detect accidental corruption caused by transport, storage, or intermediate processing problems.
Upload checks When upload integrity checking is enabled, TntDrive calculates a checksum before sending the file. For storage systems that support checksum headers, the checksum is sent with the request and the storage service validates it. TntDrive also stores checksum metadata when possible, so the value can be used later during download verification. Checksum calculation requires reading the file, so very large uploads may take longer. SHA-256 is the recommended default for modern Amazon S3 and S3-compatible storage providers.
Download checks When download integrity checking is enabled, TntDrive compares the downloaded file with the checksum available in object metadata or service response headers. If a checksum is available and does not match, the download is treated as corrupted. There are two modes for files without a usable checksum. Flexible mode accepts such files. Strict mode requires a valid checksum and reports files with missing or invalid checksum data as corrupted.
Recommended settings For most users, enable upload checks and use SHA-256. Enable download checks when the extra verification time is acceptable or when data integrity is more important than maximum throughput.
| 
