Hyper-V 2016 CSV IOPS Monitoring Incorrect?

[pterpumpkin]

Hi everyone!

I believe that Veeam ONE is using the '\Cluster CSV Files System(VolumeX)\Read/sec' and '\Cluster CSV Files System(VolumeX)\Writes/sec' counters instead of '\Cluster CSV Files System(VolumeX)\IO Read/sec' and '\Cluster CSV Files System(VolumeX)\IO Writes/sec' for Hyper-V 2016.

The latter will match the combined total of IOPS used by VM's on the volume, the former will not.

For example, for all VMs on Volume1 for our environment, we see a combined average total of ~100 IOPS. If i monitor 'Writes/sec' performance counter, it can spike massively to 30,000+ IOPS, whereas the 'IO Writes/sec' counter would match the ~100 IOPS.

I am finding it difficult to find the technical difference between these two counters, but that's definitely what we have observed.

Interestingly, our Hyper-V 2012 R2 environments show the correct numbers, it's only Hyper-V 2016 that does not.


Cheers,
Pter.

[Shestakov]

Hi Pter,
That's an interesting observation.
Could you contact Veeam support team to double-check with them if the issue exists?
Thanks!

[pterpumpkin]

Thanks! I have created a case but not getting too much traction.

I will update the thread when i get a result.

[Shestakov]

Thanks for the update.
Please provide your support case number so we can follow the investigation.

[pterpumpkin]

I think it was #00000000001 because it was that long ago.

[Shestakov]

So you were the first one who had difficulties with Veeam products
If you find the actual case number please post it as well.
Thanks!

[yara12]

did you get the result?

[pterpumpkin]

Hi yara12!

Yes, we ended up getting a custom fix for this, which brought up additional counters if you selected "Custom..." from the "Chart views". This was back in March 2018 and we were told a proper fix would be released "in the next update".

I will PM you the case number.



pter

[Shestakov]

pterpumpkin, could you provide a case number here?
It's safe as no one except Veeam R&D and Support can observe it. But other users may refer to the number if they have same issue.
Thanks!

[pterpumpkin]

Hi Shestakov,

No problem. Case number is #02607209.


Pter.

[Shestakov]

Thanks for the update Pter.
We will chime in once our assistance is needed.