Feature Request: Display VMs Involved in Historical Job Failures

[eleroy17]

Hi Team!

We would like to request an enhancement for Veeam ONE reporting capabilities.

Currently, when a backup job fails before processing any virtual machines, the Job History report correctly displays the failed execution; however, it does not provide visibility into the virtual machines associated with the failed job execution. According to Veeam Support, if the "Objects Processed" value is zero, no VM details are included in the report.

From an operational and audit perspective, it is important to identify which virtual machines were associated with jobs that experienced failures, even when the failure occurred before VM processing started.

Additionally, we observed that:

The daily report generated by Veeam ONE does not display the list of VMs involved in failed job executions.
The notification email that normally provides job and VM execution details was not received during the validation process, limiting the ability to identify affected VMs through alternative means.

Requested Enhancement:

Provide a mechanism to identify the virtual machines associated with failed job executions, including scenarios where the job fails before processing any objects.

Possible implementation options:

Add the affected VM list to the existing Job History report.

Develop a new report specifically focused on VM-level visibility for historical job failures.

Business Justification:

This enhancement would improve audit compliance, operational troubleshooting, incident investigations, and reporting accuracy by providing complete traceability of workloads potentially impacted by backup failures.

[RomanK]

Hello eleroy17,

Have you checked the Workload Protection History report?
It is the best report for auditing VM backups. You can filter workloads by status and type within the report and use the Success and Failure Rates History chart as an SLA metric for your backups.

Please take a look and let us know if this is what you are looking for.

Thanks

[eleroy17]

Hello,

I am currently validating the report, and it still exhibits the same behavior. The report does not display information about the VMs affected by this specific failure scenario.

In cases where the job fails before any VM processing begins, there is no visibility into which VMs were associated with the failed job. This is the main gap we are trying to address from an auditing and reporting perspective.

[RomanK]

Hello eleroy17,

Interesting
Сould there be a specific example to help us understand the exact reason a VM wasn't processed? Is there any information available on the VBR side? I'd like to try reproducing it and see this behavior in the lab.
It's possible that the VBR server itself didn't return anything to us, which is why we don't see it either.

Thanks

[eleroy17]

Copilot said:

Hello Romank,

The job fails immediately, so it remains in the initial phase and does not get far enough to identify or process the VMs.

In Veeam ONE, the job is correctly reported as failed; however, the report does not display the affected VMs, which is the information requested by our audit team.

The error is:
Failed to start job [JOB_NAME] Error: RPC deadline: [DATE and TIME] for invocation of VeeamBackupService._ Initialize_ has been exceeded. RPC start: [DATE and TIME]