Operational Defect Database

BugZero found this defect 4665 days ago.

Veeam | kb1013

Reported CPU Usage Values Differ in vCenter and Veeam ONE

Last update date:

12/13/2023

Affected products:

Veeam ONE

Affected releases:

ALL

Fixed releases:

No fixed releases provided.

Description:

Challenge

The reported maximum, minimum, and average CPU usage values do not match between the vCenter and Veeam ONE.

Cause

How the Values Are Calculated in vSphere Client VMware calculates these values with Hyperthreading Technology enabled. The VMware vSphere client shows that “Hyperthreading” is in the “Active” state under the “General” section on the Summary tab for the ESX(i) host within the virtual infrastructure: As a result, the “Advanced” performance page for this host shows total values for all processors but with the Hyperthreading feature enabled. Once all object are selected under the Chart Option window, the CPU Usage is displayed for all virtual CPUs and the ESX(i) host itself. Summing up the average values of each virtual CPU and then dividing by the number of virtual CPUs produces a value approximately two times smaller than the TOTAL CPU Usage value for the host.   How the Values Are Calculated in Veeam ONE Veeam ONE calculates the total CPU Usage without using VMware’s “Total CPU Usage for entire host with Hyperthreading enabled” option. It takes each CPU's Usage and then performs calculations as described above. Thus, in Veeam Monitor, the Total CPU Usage value is two times smaller than CPU Usage for the entire host on VMware’s graphs.

Solution

No solution required as this is the expected behavior.

More Information

If you have any questions or problems, please contact Veeam Support.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...