Welcome to the forum @llkbennprz
See Upload throttle corrupts backup, especially OneDrive. Analyzed, with code proposed. #3787
If you happen to have your old backup (after starting the new one) you can look for its symptoms multiple ways as listed earlier. If you can identify the bad file, you can look at it with a hex viewer.
Commonly, it seemed like larger files such as the default 50MB dblock were more likely to get hit. Dblock file problems are worse than dlist and dindex because the latter can be fixed by individual manual delete and then Repair. Assuming the problem isn’t in the DB by Recreate, DB will fix file.
Dblock files are the file data so for example, if damage is to a file now deleted, its backup is gone.
The AFFECTED command can show what the loss of a given destination files means to a backup.
Fix implementation of ThrottledStream.Write #3811 was the fix. Throttling even once could have damaged some files, and usually not throttling would mean that they might take awhile to notice, although verification does try to test-balance its sample, so I’d have expected it to notice sooner.
Regardless, that’s my guess for OneDrive throttle issue that comes back in the form of bad files. Additional information might be able to refine or refute it. There’s no beta yet with that throttle fix.
This might be what you want (I’m not 100% certain), but in practice it didn’t work. It’s now off by default. I’m also noticing that the Advanced Options doesn’t show that option, but now it’d need to be re-tested:
v2.0.3.10-2.0.3.10_canary_2018-08-30
Removed automatic attempts to rebuild
dblockfiles as it is slow and rarely finds all the missing pieces (can be enabled with--rebuild-missing-dblock-files).