Hello everyone,
Azure Local Cluster 4 Nodes: Some backup jobs are no longer working.
Backups are performed via the SCVMM object.
A new backup job via the cluster object worked.
The following messages appear during backups:
First this one:
Error: Failed to collect VM information. [WMI] Empty result.
Then this one appeared:
Unable to allocate processing resources. Error: On-host proxy requires upgrade before it can be used.
The only change to the environment was Windows Updates January 13, 2026 on the backup server B&R 12.3.2 (Server 2022) and SCVMM (Server 2025).
Otherwise, the cluster and VMs are running stably. VMs and CSV files are OK. Azue Local is up to date. It is updated regularly every month.
I would try uninstalling the last monthly Windows update. But I'm not a fan of that.
Maybe someone has an idea why it stopped working?
Veeam Support - Case # 07952826
Best regards
Daniel
-
_tcpip_
- Novice
- Posts: 4
- Liked: never
- Joined: Sep 28, 2023 1:33 pm
- Contact:
-
david.domask
- Veeam Software
- Posts: 3243
- Liked: 753 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Error: On-host proxy requires upgrade before it can be used
Hi Daniel,
No known issues related to the update, so please continue with Veeam Support on the troubleshooting.
I would advise wait for Support's update before uninstalling the update to understand why these errors suddenly appeared -- the WMI error basically tells that when we made a WMI query no information was received, though for unclear reasons, and I see Support gave a few suggestions to start with but looks like those initial suggestions didn't work.
Please continue with Support, they should update the case soon. If you have concerns about the case handling, please use the Talk to a Manager button in the case portal to reach out to Support Management, they will review the case and allocate additional resources as necessary.
No known issues related to the update, so please continue with Veeam Support on the troubleshooting.
I would advise wait for Support's update before uninstalling the update to understand why these errors suddenly appeared -- the WMI error basically tells that when we made a WMI query no information was received, though for unclear reasons, and I see Support gave a few suggestions to start with but looks like those initial suggestions didn't work.
Please continue with Support, they should update the case soon. If you have concerns about the case handling, please use the Talk to a Manager button in the case portal to reach out to Support Management, they will review the case and allocate additional resources as necessary.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: No registered users and 170 guests