Dear Veeam Team,
We are currently using Veeam Backup & Replication (VBR) to back up our virtual machines and Veeam ONE for reporting and monitoring purposes.
Some of our servers have multiple large-sized disks, and to manage backup efficiency, we have split these disks across multiple backup jobs—typically, one job per disk.
Our requirement is to generate a report from Veeam ONE that shows protection status at the disk level. The goal is to ensure that all disks attached to a VM are being backed up, and none are unintentionally left out of the configured jobs.
At present, the available Protected VMs report checks protection only at the VM level. For example, if a VM has five disks and just one of those disks is included in a backup job, the report still considers the entire VM as protected. In reality, this leaves four disks unprotected, which poses a significant data risk.
We strongly believe that the ability to report on backup coverage at the individual disk level would greatly enhance the value of Veeam ONE and help ensure more accurate data protection strategies, especially in complex environments.
We appreciate your attention to this request and hope to see this functionality included in a future release.
Regards,
Prakash Veluchamy
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jun 04, 2025 6:02 am
- Full Name: Prakash Veluchamy
- Contact:
Feature Request – VM Disk-Level Protection Reporting in Veeam ONE
Regards,
Prakash Veluchamy
Prakash Veluchamy
-
- Veeam Software
- Posts: 795
- Liked: 206 times
- Joined: Nov 01, 2016 11:26 am
- Contact:
Re: Feature Request – VM Disk-Level Protection Reporting in Veeam ONE
Hello Prakash,
You are right - VMs are considered protected if they have at least one restore point within the RPO.
In your case, with the "one job per disk" approach, I’d recommend checking job-level reports and backup job statuses, such as Job History or Workload Protection History, grouped and scheduled by job names.
In the current version of Veeam ONE, it might be a complicated task to group by job name for the big environment. However, we are expecting a significant improvement in report flexibility in upcoming releases to cover this use case.
Thanks
You are right - VMs are considered protected if they have at least one restore point within the RPO.
In your case, with the "one job per disk" approach, I’d recommend checking job-level reports and backup job statuses, such as Job History or Workload Protection History, grouped and scheduled by job names.
In the current version of Veeam ONE, it might be a complicated task to group by job name for the big environment. However, we are expecting a significant improvement in report flexibility in upcoming releases to cover this use case.
Thanks
Who is online
Users browsing this forum: No registered users and 1 guest