More often than not, I get byte-to-byte compare errors (see below) on a long-ish backup. The target drive is a Seagate USB, and I have run Seagate's low level diagnostics to show the drive is clean. I have also run the Microsoft Win10 memory tester, and memory is clean, too.
Per this article (https://www.terabyteunlimited.com/kb/article.php?id=151
), I have verified that "Omit $UsnJrnl Data" is set. I have also noted that the user manual heavily recommends using VSS on Windows systems, so I do. I don't see the value of *not* comparing byte-for-byte, so turning off comparisons seems like a pretty bad idea.
So, any idea why these errors keep happening and what I can do to eliminate them?
Here's the command line the scheduler executes:
"E:\Sysprog\TeraByte Drive Image Backup and Restore Suite\imagew64.exe" /wait /b /uy /um /d:w1 /f:"J:\MThor\Backup-w1-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /v /vb /comp:2
I'm running IFW 3.32.
[10/6/2019 1:33:08 AM] Validating: Windows Partition (03) 95795 MiB NTFS
[10/6/2019 1:33:08 AM] From: J:\MThor\Backup-w1-2019-10-06-0100.TBI
[10/6/2019 1:33:08 AM] Byte-for-Byte failure at LBA 567296 offset 0 (0)
[10/6/2019 1:33:08 AM] Byte-for-Byte failure at LBA 567297 offset 0 (512)
[10/6/2019 1:33:08 AM] Byte-for-Byte failure at LBA 567298 offset 0 (1024)
... etc ...