Veeam not seeing all VM's on NetApp SAN.

[jbarrow.viracoribt]

Trying to use the Storage Infrastructure browser to recover a file from a snapshot on a NetApp SAN.

The VM I'm looking for isn't listed at all, the latest snapshots show 45 VM's within the snapshot from the Veeam console.



When I look at the LUN from within VMware, I see 47 VM's (which have all been there for days or weeks now).



So what gives? Is this a Veeam issue or a NetApp issue? Not sure how to confirm which device/system is at fault here.

Ticket 00996470

[foggy]

Jonathan, not sure about VMware, but Veeam B&R console shows VMs by the number of .vmx files on the datastore. Any chance some VMs with disks residing on this datastore have their .vmx files somewhere else?

[jbarrow.viracoribt]

Nope, this VM, VLSERVER2 is all on the NetApp LUN only.

[foggy]

Then I'd wait for what our engineers could tell after reviewing the logs you've provided.

[jbarrow.viracoribt]

Yeah, the case is not moving, my ticket has been opened since 8-13 (2 weeks) and we don't seem to have much luck getting any insight, that's why I posted here.

[veremin]

What about escalating the case by clicking "Talk to a Manager" button on the customer support portal? Have you tried that already?

[jbarrow.viracoribt]

What about escalating the case by clicking "Talk to a Manager" button on the customer support portal? Have you tried that already?

No but I will. Thanks.

[Gostev]

Subscribing since I am curios what is the issue here... but this most certainly will be a Veeam issue here, unless those missing VMs simply have an unsupported config. I assume you have already tried full rescan at root node of the Storage Infrastructure tab?

[jbarrow.viracoribt]

Subscribing since I am curios what is the issue here... but this most certainly will be a Veeam issue here, unless those missing VMs simply have an unsupported config. I assume you have already tried full rescan at root node of the Storage Infrastructure tab?

Yes, it has been rescanned a few times.

Not sure what an unsupported config would be in this environment. Veeam backs up the missing VM without issue, if that helps at all.

[Gostev]

OK. In that case, it does sound like a bug on our side.