Hello!
Am I correct that the disk was removed from the server (VM); but the VM itself still exists?
There could be a stale performance metric somewhere in the pipeline for that disk, stuck reporting the last known value. However it could be anywhere, from vSphere via Collector to WMI to SCOM....
I'll check with the team where this data might be located (you have already tried the first troubleshooting steps!)
However in the meantime you may be able to suppress the alerts.
If the alerts are coming from monitor "Veeam VMware: Virtual Machine Disk Space Analysis", then you can use an override on this monitor to exclude certain disks by volume name.
You can override the parameter "Exclude Disks" to add the required volume name. The parameter supports regular expressions. The default setting is:You can simply add your own volume to the start of this list, followed by the OR character (pipe). E.g to exclude volume X: use -As with all overrides, you can apply it per-VM, per-group, or globally.
Hope that helps!
Am I correct that the disk was removed from the server (VM); but the VM itself still exists?
There could be a stale performance metric somewhere in the pipeline for that disk, stuck reporting the last known value. However it could be anywhere, from vSphere via Collector to WMI to SCOM....
I'll check with the team where this data might be located (you have already tried the first troubleshooting steps!)
However in the meantime you may be able to suppress the alerts.
If the alerts are coming from monitor "Veeam VMware: Virtual Machine Disk Space Analysis", then you can use an override on this monitor to exclude certain disks by volume name.
You can override the parameter "Exclude Disks" to add the required volume name. The parameter supports regular expressions. The default setting is:
Code:
A:\\|B:\\|/boot|C:\\VeeamFLR\\.* Code:
X:\\|A:\\|B:\\|/boot|C:\\VeeamFLR\\.*Hope that helps!
Statistics: Posted by Alec King — May 12, 2026 12:09 pm
