Host-based backup of VMware vSphere VMs.
Post Reply
Hela
Lurker
Posts: 1
Liked: never
Joined: Aug 20, 2025 7:16 am
Full Name: Tanguy FOURNIER
Contact:

Backup job succeeds even when VM with NVDIMM device is skipped (no error reported in console)

Post by Hela »

Hello,

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.
Feature Request:
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.
Thank you for considering this request.
david.domask
Veeam Software
Posts: 2920
Liked: 669 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: Backup job succeeds even when VM with NVDIMM device is skipped (no error reported in console)

Post by david.domask »

Hi Hela, welcome to the forums.

Veeam's behavior here is to warn on the first backup of such VMs within a job and subsequent runs will not produce a warning.

This design was based on user feedback as previously it would warn on every run and create needless work as such VMs were known to have unsupported configurations by the backup administrators and making the entire session a warning was too much.

Consider using the VM Configuration Assessment Report if you use Veeam One in your environment to detect VMs that may not back up in full due to their configuration.
David Domask | Product Management: Principal Analyst
Post Reply

Who is online

Users browsing this forum: Semrush [Bot] and 22 guests