Case #07914000 — Getting VM info from vSphere for 60+ hours

[ryan.christensen]

We had a backup job that was idling at getting VM info from vSphere for 60+ hours. Why does Veeam not have a time out for this operation? I can use VSPC "Max allowed job duration" to alert on this type of failure but it seems odd to me that Veeam wouldn't fail for the single VM and move on.

Veeam logs:
Failed to init vddk access
Error (3) VDDK error: 20005 (The operation has been disabled by the guest operating system).

Thanks,

[Mildur]

Hi Ryan,

While I agree that some timeouts could be improved, I can’t confirm that your situation is one of them or that it was caused by an unexpected issue.
I’m confident our support team will determine why the timeout didn’t occur as expected and escalate the issue to R&D if needed.
Please let me know if support concludes it’s expected behavior—I’ll want to review the case in that situation.

Best,
Fabian