Skip to main content
Question

Blank Veeam Inventory VM info

  • February 19, 2026
  • 6 comments
  • 28 views
D

I have a 7 node HyperV failover cluster and each host is running Windows server 2022. I have about 20 Red hat linux VMs in my cluster and added the cluster to my Veeam inventory. Most of the VMs added sucessfully with the cluster, but about 6 of them are added with all blank fields. There's no name, no node info and the host OS says unknown. When I try to add these VMs to a backup job in Veeam 12.3.2.3, they show the accurate disk capacity on the VM page, but when I run the job they all fail. I get an error about how Veeam failed to get the VHDX information.

Many of the VMs had multiple HyperV checkpoints that were all deleted and merged. There was also an issue where our HyperV cluster had cluster traffic blocked on certain nodes in the past, which may have cause some Cluster synchronization/ownership permission.  Please advise on how to make Veeam able to read these VMs.  I understand this may be a more of a Microsoft issue, but any assistance is appreciated. 

 

      6 comments

      Tommy O'Shea
      Forum|alt.badge.img+5
      • Tommy O'Shea
      • Veeam Legend
      • February 19, 2026

      Are there any special characters in the names, or any common denominator between that that might be contributing to this?

      As always I’d also recommend submitting a ticket to Veeam Support and uploading logs and the Veeam database to them, they could see what it is about those VMs that isn’t letting them show up.

      Tommy O’Shea, VMCE, VMCE-SP, VMCA
        coolsport00
        Forum|alt.badge.img+21
        • coolsport00
        • Veeam Legend
        • February 19, 2026

        Hi ​@Deion2009 -

        Welcome to the Community! Aside from the check Tommy suggested, I recommend as he did and open a case with Veeam Support. Someone may still post some recommendation, but always best to start with Support as they can have more intimate look at your environment and logs.

        Best.

        Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
          lukas.k
          Forum|alt.badge.img+13
          • lukas.k
          • Influencer
          • February 20, 2026

          No kidding, this is very often DNS related. Can you try to use the FQDN instead of the hostname or the other way round? Please also make sure that Veeam has the domain suffix set on the VBR server.

           

          With Hyper-V - since it is all Windows OS - DNS is pain and causes really weird issues.

           

          In case that doesn’t help, I’d stick with Shane’s suggestion to open a Veeam Support ticket.

          LK | Enterprise Architect @ Veeam Software | Former Veeam Vanguard | Security Specialist
          D
          • Deion2009
          • Author
          • Not a newbie anymore
          • February 20, 2026

          Thanks all for the help. I’m in the process of getting logs to send to Veeam support for a ticket now. In the mean time, I’ll double check all the DNS records

          D
          • Deion2009
          • Author
          • Not a newbie anymore
          • February 20, 2026

          No kidding, this is very often DNS related. Can you try to use the FQDN instead of the hostname or the other way round? Please also make sure that Veeam has the domain suffix set on the VBR server.

           

          With Hyper-V - since it is all Windows OS - DNS is pain and causes really weird issues.

           

          In case that doesn’t help, I’d stick with Shane’s suggestion to open a Veeam Support ticket.

          Thanks, I’ll double check the DNS records. All of the VMs are added by cluster object, so FQDN and Hostname arent even options. I just add the cluster name and all the VMs inside automatically add. Most are fine but 6 out of the 20 are blank and Veeam can't read the .vhdx information. 

          D
          Forum|alt.badge.img+3
          • ddomask
          • Comes here often
          • February 20, 2026

          I’m doubtful it’s about DNS personally -- Veeam interacts with Hyper-V via the Hyper-V Integration service, which is basically proxying WMI calls.

           

          Most of the VMs added sucessfully with the cluster, but about 6 of them are added with all blank fields. There's no name, no node info and the host OS says unknown. When I try to add these VMs to a backup job in Veeam 12.3.2.3, they show the accurate disk capacity on the VM page, but when I run the job they all fail. I get an error about how Veeam failed to get the VHDX information.


          Would lean towards HV issue based on that, but it’s best to let Veeam Support review the logs, if it’s really WMI failures, it should be fairly clear in the Veeam logs from the Hyper-V host(s)

          0x0D 0x0A
            Terms & ConditionsAccessibility statement