Question on old KB

[wejohnson]

This KB https://www.veeam.com/kb1893

We had a repository that suffered from this issue, and we were able to fix it by reformatting with the /L option. The question I have gotten from management is how do we determine if any of other repositories will suffer from this?

Is there a tool that will search every file system record on a volume and tell you if any file is hitting the 1K or 4K limit?

[DonZoomik]

AFAIK you cannot easily determine if you'll be affected by this. You could for example analyze the file with Sysinternals contig tool to get the number of file extents but it is only a heuristic result.
However defragment should effectively fix the issue by reducing the number of file extents. If you don't want to defragment the whole file system, you could use the same contig tool to defragment the affected files.