VM stuck at "Getting VM info from vSphere"

[FMOFMO]

Thanks for the answer but no need to open a case. All my problems were gone after upgrading to version 9.5.0.711 !

[Andreas Neufert]

Thank you for the feedback.

[wirthon]

I am having the same issue with one vm. I have contacted Veeam and support couldn't find the solution.

[foggy]

What is your case ID?

[wirthon]

Case 02027705

[foggy]

As far as I can see, the investigation is going on, feel free to escalate the case if you'd like a closer look at the issue.

[wirthon]

yes its on going but we aren't getting anywhere

[foggy]

As I've mentioned, you can ask for escalation of the case to a higher tier.

[blacks4]

We are getting this and our backups have been down for a week. Nothing is working. vSphere 6.5 with a mix of 6.0 and 6.5 ESXi hosts. and every backup job, new or old, that worked perfectly before, is not working at all even on Veeam Backup & Replication 9.5.0.823 (patch just applied today).

I went to "Backup Infrastructure", selected our vCenter server and rescanned it successfully. no errors.

I've opened backup jobs and "recalculated" them successfully (no errors).

I've rescanned all backup Repo's successfully (no errors).

When I start a backup job even to a local repository on the same physical Windows server, and only backing up 1 Linux vm that is TURNED OFF (or on, doesn't matter), it starts, creates 2 initial files in the repo folder:

<backup job name>.vbm (which is 7KB)
<backup job name><timestamp>.vbk (which is 30866KB)

then it just sits forever:

"Hard disk 1 (0.0 B) 0.0 B read at 0 KB/s [CBT]"

Case #02044544

PLEASE HELP

[m_zolkin]

Support team is reviewing Case #02044544 and we'll update you with our findings shortly.

[blacks4]

Update for those still having problems: our case isn't 100% resolved, but a temp workaround that's allowing us to backup servers in the meantime was to create a new proxy on a different system, and specify that in our backup jobs. Something with the locally installed proxy and local Transport software isn't happy but at least we can backup now. If you're in a bind and nothing else is working, might as well give it a try.

[Andreas Neufert]

Did you cloned the non-working Proxy at some point time in the past?
Is it a Win 2008 (R2) system?

[CharadeUR]

Any resolution to this case? We are having the same problem. I know open a support case. Seems like a common enough issue it should be resolved by now.

[EugeneK]

Based on the variety of possible reasons it may be not working, I'd recommend to still open a support case and let support take a look into it.
Did you happen to try the workaround with a dedicated Proxy installed to see if it addresses the particular issue you're having?

[whatever]

we had the same probs with our Veeam machine.
all backup and replication jobs got a timeout while reading disks....

workaround: install a new proxy server on any VM, get it in Veeam, choose only this proxy in jobs (and maybe fix ip-adresses)

works great now!!!

[Delo123]

@Veeam Does this have anything to do with the local proxy not using the networkor not? I remember there was a hiddeen reg setting for that in 9 but can't remember if loopback processing is now fully supported and "networkless" now

[Vitaliy S.]

Guido, no this shouldn't be the reason for this issue, let our support team investigate this further.

[m.novelli]

I've got about three - four customers in the last month with this issue, the backup stuck since some days on "Getting VM info from vSphere". Veeam 9.5 Update 3a with vSphere 6.0 U3 updated to early - mid 2018

I've opened a ticket, case #03235970

Cheers