Yeah, something is clearly not in order here. From the bottleneck stats indeed it does not look like Veeam is the issue here... our data mover spends all the time just waiting for the storage to provide the requested data blocks, while the rest of the processing chain is completely idle.
paps40 wrote:Veeam support mentioned everything looked good on the Veeam End.
Did they perform some basic I/O performance tests using other tools?
Was the speed in these tests roughly the same as during backup?