We recently encountered a problematic behavior in Veeam Backup & Replication. One of our VMs was not being backed up, but the job still reported Success in the Veeam console with no warning or error.
After investigation (then confirmed with Veeam Support, Case # 07797800), we found that the root cause was the presence of a virtual NVDIMM device with disks engaged in SCSI bus sharing, which prevents snapshot creation. As documented, such configurations are not supported for VM backup, and the recommendation is to use Veeam Agent instead.
The issue is not about the lack of support itself (we are aware that NVDIMM devices cannot be backed up with standard VM jobs), but rather the lack of error visibility:
- The VM is silently skipped.
- The overall job status remains “Success” instead of at least a “Warning” or “Failed”.
- This creates a major risk: administrators may assume all VMs in the job are protected, only to discover during restore that one VM has never been backed up.
It would be very valuable if Veeam Backup & Replication could:
- Report an explicit warning/error in the console and job summary when a VM cannot be backed up due to unsupported devices (like NVDIMM).
- Ensure the job result reflects the fact that not all VMs were successfully protected.
- This would greatly improve visibility and prevent situations where critical workloads are left unprotected without the administrator noticing.