Skip to main content
Question

Infrastructure load report - no recent values

  • Nov 18, 2026 2:58 PM UTC
  • 3 replies
  • 17 views

Forum|alt.badge.img+13

Hi guys,

can you tell me, what might be the reason for the CommServe to stop adding values to the database table [HistoryDB].[dbo].[MMPerformanceHistory], that is one of the sources for the Infrastructure Load Report.

since yesterday, new values are no longer added for some (not all) of the media agents.
As a result, I can no longer see the CPU Utilization of all my AccessNodes and MediaAgent, but only for some.

didn’t change anything in the configuration.

currently only the CommServe client is still adding values.
All my media agents have been fading away during the last 24 hours (not all of them at the same time)

Operating on 11.36.130

rgds
Klaus

3 replies

Forum|alt.badge.img
  • Vaulter
  • Nov 18, 2026 4:14 PM UTC

Hi Klaus,

Since 11.36.130 is already the latest maintenance release.

A few things worth checking:

  • Confirm the affected MediaAgents are online, communicating with the CommServe, and otherwise functioning normally for backup/restore operations.
  • Compare the last successful performance-data timestamp for each affected MediaAgent with any service, OS, or network events around the same time.
  • Check whether only CPU utilization stopped updating or whether memory and other performance metrics stopped as well.
  • Verify whether there were any OS, firewall, security, or network changes around the time the issue started, even if no Commvault configuration was changed.

The Infrastructure Load Report documentation confirms that the report displays CPU and memory resource information collected for the CommServe and MediaAgents. Commvault documentation [documentat...mvault.com]

Since the MediaAgents stopped reporting at different times while the CommServe continues to report, comparing the last successful collection time for each affected MediaAgent may help identify a common pattern.

If the MediaAgents are otherwise healthy and only performance-data collection has stopped, I would suggest opening a Commvault Support case for further investigation. I would also avoid making any manual changes to HistoryDB or MMPerformanceHistory while troubleshooting.


Hope this is helpful!


Forum|alt.badge.img+13
  • Author
  • Challenger
  • Nov 18, 2026 4:26 PM UTC

Hi ​@Karthick R ,

Media Agents are operating properly.
Absolutely noc operational issue visible.

I only look at the mentioned table and see, that updates with new data are no longer executed/added.
I don’t know what process is responsible or where to find additional logs regarding this.

the CPU and Memory load is part of the same table. Therefore both values are missing, since there are currently no new entries for the media agents clientIDs. 

if this persists a restart of the CommServe, I will open a support ticket to get this properly analyzed.

thanks
Klaus


Forum|alt.badge.img
  • Vaulter
  • Nov 18, 2026 4:29 PM UTC

Thanks Klaus, that makes sense.

If the MediaAgents are operating normally and there are simply no new MMPerformanceHistory entries for those client IDs, this looks more specific to the performance-data collection/update process.

If the CommServe restart does not restore the updates, I agree that a Support case would be the right next step. I would include the last successful timestamp and client ID for a few affected MediaAgents, as they stopped reporting at different times. That should give Support a useful correlation point for the CommServe-side logs.

Please keep us posted on the outcome.