Hi,
Since upgrading to Veeam ONE v13, we noticed a significant change in the Successful Backup Ratio calculation that affects Job History and Workload Protection History reports.
What changed in v13:
Jobs finishing with a Warning status and 0 processed objects ("Nothing to process") are now counted in the total executed jobs (denominator) but excluded from successful jobs (numerator), directly lowering the reported success percentage. In v12 these sessions were handled differently and did not penalize the ratio.
This behavior has been confirmed by Veeam Technical Support as intentional and by design in v13.
Impact:
In our environment we have long-retention jobs (Diamond, Platinum, Gold schedules) that run daily but find no eligible VMs on most executions. Each of these Warning/0-object sessions now penalizes the daily success rate. In our analysis of April 2026 (1,357 job runs), this single factor accounts for approximately 9 percentage points of difference between the reported rate and the actual operational protection rate.
Feature Request:
We would like to request the ability to either:
Exclude Warning sessions with 0 processed objects from the Successful Backup Ratio calculation, or
Allow administrators to configure which session types are included in the denominator
This would restore the metric to a meaningful representation of actual backup health, consistent with v12 behavior.
Thank you for considering this request.
Case #08089302
Since upgrading to Veeam ONE v13, we noticed a significant change in the Successful Backup Ratio calculation that affects Job History and Workload Protection History reports.
What changed in v13:
Jobs finishing with a Warning status and 0 processed objects ("Nothing to process") are now counted in the total executed jobs (denominator) but excluded from successful jobs (numerator), directly lowering the reported success percentage. In v12 these sessions were handled differently and did not penalize the ratio.
This behavior has been confirmed by Veeam Technical Support as intentional and by design in v13.
Impact:
In our environment we have long-retention jobs (Diamond, Platinum, Gold schedules) that run daily but find no eligible VMs on most executions. Each of these Warning/0-object sessions now penalizes the daily success rate. In our analysis of April 2026 (1,357 job runs), this single factor accounts for approximately 9 percentage points of difference between the reported rate and the actual operational protection rate.
Feature Request:
We would like to request the ability to either:
Exclude Warning sessions with 0 processed objects from the Successful Backup Ratio calculation, or
Allow administrators to configure which session types are included in the denominator
This would restore the metric to a meaningful representation of actual backup health, consistent with v12 behavior.
Thank you for considering this request.
Case #08089302
Statistics: Posted by charlieferreiracln — May 11, 2026 3:42 pm
