#1 Global Leader in Data Resilience

"Backup performance data collection failure"

KB ID: 2269
Product: Veeam ONE | 12 | 12.1 | 12.2 | 12.3
Published: 2017-04-10
Last Modified: 2025-04-07
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

Veeam ONE raises the Backup performance data collection failure alarm.
Alarm
Example 1 - Performance data cannot be collected from the repository associated with Veeam Backup & Replication.
Perf Data Collection HVHost
Example 2 - Performance data cannot be collected from a Hyper-V host managed by Veeam Backup & Replication.
When this alarm occurs, it is critical to pay attention to the "source" or "object" specified in the message, as that is the resource from which Veeam ONE is failing to collect performance data.

Cause

This alarm occurs when Veeam ONE fails to collect performance data from the specified Source/object associated with a Veeam Backup & Replication or Veeam Backup for Microsoft 365 server.

Solution

Read the Alarm Details

Select the Veeam Backup & Replication or Veeam Backup for Microsoft 365 server and review the Alarm Details on the Alarms tab. These details will often include additional information to help troubleshoot the issue.

Example

In this example, the Hyper-V server managed by the Veeam Backup & Replication server cannot be accessed by Veeam ONE because the credentials to connect to the Veeam Backup Server are different than the Hyper-V server. In such a scenario, the individual server must have credentials assigned within Veeam ONE to allow it to connect.
set creds

Additional Connection Troubleshooting Advice

The following are things to check related to the source or object specified in the alarm:

  • Verify that the account used to connect to the source or object is valid and has the correct permissions.
    To check the account name, right-click on the object that the alarm is alerting for, and select Connection Settings. Note the specified account.
  • Review firewall requirements requirements, checking those that match the type in the To column with that specified in the alarm.
    Hint: Review the Firewall PowerShell commands in the More Information section of KB2266.
  • If the alarm specifies a Windows machine, ensure that the following services are running on that remote machine:
    • Windows Management Instrumentation
    • Remote Procedure Call
    • Remote Registry
  • Use Windows Management Instrumentation Tester to test WMI connectivity from the Veeam ONE server to the remote machine.

More Information

If the issue persists, collect Veeam ONE log files and open a support case. It is recommended that you provide the whole content of the log folders to ensure that all comprehensive information is provided to the support team for analysis.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.