Hi, I’m trying to back up a VM running on a standalone ESXi v8 host using Veeam B&R v12 Community edition. When I set the job up it ran successfully but all subsequent (scheduled) backups fail with “Failed to create processing task for VM Sophos Firewall Error: No proxy available”.
If I edit the job without changing anything (just applying the same settings) it will run. Also, if I do the same with the VMWare Proxy object or the veeam server object (in Backup Infrastructure > Managed Servers) it will also run. In all cases it will only run the first time after applying the settings. Again, all subsequent runs fail.
The veeam ‘server’ is an i3 8GB Windows 10 22H2 x64 PC. What looks to be the root cause is an entry in the job backup log that says:
aProxyDetector] VMware host API version is V800. Skipping not x64 proxies 4ProxyDetector] VMware host API version is V800 and all available proxies are not x64 so we can not use it with such API version
I’m not sure what to do with this; Where do I get the x64 VMware proxy from? I assumed the installer would install the bitness version that matches the OS, and the OS is definitely x64. I also don’t understand why it works on the next backup after modifying any of the components, but not subsequent runs.
Thanks in advance.
Page 1 / 2
Not sure why this would fail based on your OS for the Veeam server but do you have a Windows machine on the ESXi host that is x64 that you could add as a Proxy and see if that helps?
Further to what @Chris.Childerhose mentioned, are you using a particular transport mode? Are you able to provide any screenshots of the settings and error messages?
Hi @dav.san - though documentation supports Windows 10 OS as a host for VBR and being used as a Proxy, there was a known issue noted in the forums, specifically with Win7/8, which seemed to also affect Win10, which may be what you’re running into. Not exactly your error, but may be related a bit. Also, it seems someone else posted here in the Hub who ran into a simiar issue, tho their problem was related to Win2022 Server.
I didn’t really see much anywhere posted about this error searching the Internet. Aside from trying what Chris suggests (creating a Windows or Linux VM to use as a hotadd transport Veeam Proxy), and seeing if that works better for you, I can only suggest contacting Support to see if they’ve run into this & if there’s a fix.
Thanks both for responding.
I don’t think the ESXi host has enough resources for a Windows VM, it’s one of those fanless PCs that look more like a giant heatsink, so resources are plenty for SF, but not much more I’m only running ESXi on it because Sophos Firewall doesn’t recognise consumer 2.5Gbe NICs natively, so have to run it as a VM. (my original intention with this PC was to run it natively)
Using Network transport, manually selected in the Proxy. Auto throws the same error.
I’m backing up to an iSCSI target on my NAS, mapped to the Veeam server on drive F:
Proxy screenshots:
Error:
Incidentally, I’ve also wiped and reinstalled Win 10 x64 from a new installer that only had x64 installation media on it. This is also the part of the log that mentions bitness:
>02.09.2023 02:00:24.241] <01> Info ViVmStorageIntegrationChecker] Detecting DirectNFS compatibility for backup 'Sophos Firewall' VM V02.09.2023 02:00:24.257] <01> Info ViVmStorageIntegrationChecker] Backup VM 'Sophos Firewall' is DirectNFS compatible. r02.09.2023 02:00:24.319] <01> Info nProxyDetector] VMware host API version is V800. Skipping not x64 proxies 602.09.2023 02:00:24.319] <01> Info tProxyDetector] VMware host API version is V800 and all available proxies are not x64 so we can not use it with such API version c02.09.2023 02:00:24.350] <01> Error Task failed. 02.09.2023 02:00:24.350] <01> Error No proxy available (System.Exception) s02.09.2023 02:00:24.350] <01> Error at Veeam.Backup.Core.CViProxyDetector.GetValidProxies(IViBackupProxyo] allProxies, EApiVersion apiVersion, Boolean skipErrors) e02.09.2023 02:00:24.350] <01> Error at Veeam.Backup.Core.CViProxyDetector.DetectForBackup(CHost host, CVm vm, IViBackupProxyk] availProxies, CHierarchyCache cache, CDiskFilter diskFilter, ISessionLogger logger, CProxyDetectDirectNfsOptions isDirectNfsAllowed, CProxyVmCache proxyVmCache) w02.09.2023 02:00:24.350] <01> Error at Veeam.Backup.Core.CViProxyBuilder.BuildViProxyies(CViVmContext viVmContext, CBackupTaskSession taskSession, CProxyVmCache proxyVmCache) k02.09.2023 02:00:24.350] <01> Error at Veeam.Backup.Core.CViTaskResourceBuilder.BuildSourceProxyResources(CViVmContext viVmContext, CBackupTaskSession taskSession, IReadOnlyList`1 allProxies, CProxyVmCache proxyVmCache) `02.09.2023 02:00:24.350] <01> Error at Veeam.Backup.Core.CViTaskResourceBuilder.BuildDiskResources(CResourcesContainer resources, CBackupTaskSession taskSession, VmEntry vmEntry, IViReplicaVmSpec vmSpec, CViVmContext viVmContext, IReadOnlyList`1 allProxies, CProxyVmCache proxyVmCache) y02.09.2023 02:00:24.350] <01> Error at Veeam.Backup.Core.CViTaskResourceBuilder.CreateResourceData(CViVmContext viVmContext, CBackupTaskSession taskSession, IViReplicaVmSpec vmSpec, Guid objectId, Boolean useVss, IReadOnlyList`1 allProxies, CProxyVmCache proxyVmCache) a02.09.2023 02:00:24.350] <01> Error at Veeam.Backup.Core.CViTaskBuilder.CreateViVmTasks(CViTaskBuilderEntry entry, CVcdTaskInfo vcdTaskInfo, IViReplicaVmSpecBuilder vmSpecBuilder, IInitialTaskCreator initialTaskCreator, IReadOnlyList`1 allProxies, CProxyVmCache proxyVmCache)
Did you use ‘Automatic Selection’ as your transport mode previous to configuring/testing Network mode? Does using Automatic give you the same result?
Nothing really stands out from your logs. Only suggestions I can offer is attempt to add a x64 Windows or Linux virtual machine as a Proxy to your VBR server and use it for your job to see if you have better success, and/or contact Veeam Support. They do support free Community Edition.
It’s not free version of ESXi is it? As that’s not supported as per the help centre as the api’s needed are disabled.
That’s a good catch Mark! Could very well be that.
@MarkBoothman No, it’s licensed through work for my lab.
Didn’t realise that Veeam support the community edition, pretty sure they say on the download page that they don’t, but I’ll give it a shot.
Are there any guides on setting up a new server as a proxy, as I think that’s also worth a shot and I didn’t realise you could offload components to other servers.
Thanks everyone for your responses, didn’t expect anything so quick!!
For a Proxy, just create a basic Windows/Linux VM on your Host. Then, on your VBR server, in Backup Infrastructure node, rt-click Managed Servers > Add Server & select Windows/Linux. Just go through the brief wizard. Next, go up to Backup Proxies, rt-click > Add Proxy > VMware Backup Proxy, and go through the wizard. In your Backup job, rt-click > Edit it and under the Storage option, choose your new Proxy. Re-run your job and see if it works for you.
Just adding an update to this in case anyone else comes across this issue;
I installed the hyper-v role onto the veeam server and set up a slim CentOS 7 VM. Added it to the managed servers list and then created a new VMware Proxy using this VM. All as suggested by the helpful people above. Many thanks to them.
Worked a treat. Manual backup and the scheduled backup completed successfully.
Now…. as any IT Pro would feel, this is great, but I still want to know why the veeam server isn’t working as its own proxy, if indeed it should…..
Just adding an update to this in case anyone else comes across this issue;
I installed the hyper-v role onto the veeam server and set up a slim CentOS 7 VM. Added it to the managed servers list and then created a new VMware Proxy using this VM. All as suggested by the helpful people above. Many thanks to them.
Worked a treat. Manual backup and the scheduled backup completed successfully.
Now…. as any IT Pro would feel, this is great, but I still want to know why the veeam server isn’t working as its own proxy, if indeed it should…..
It might be worth logging a ticket with Veeam Support and see if they are able to provide an insight into what might be causing the issue.
Hello, unfortunately, I am experiencing the same problem. An error has occurred out of nowhere. I have not been able to solve it for 3 days. What is the exact solution?
[01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies r01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version o01.11.2023 04:33:51.310] <01> Error Task failed. a01.11.2023 04:33:51.310] <01> Error No proxy available (System.Exception)
Hello, unfortunately, I am experiencing the same problem. An error has occurred out of nowhere. I have not been able to solve it for 3 days. What is the exact solution?
[01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies 01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version n01.11.2023 04:33:51.310] <01> Error Task failed. i01.11.2023 04:33:51.310] <01> Error No proxy available (System.Exception)
Based on the errors posted did you check your proxy servers? It seems like there is not a proxy that can communicate with the VMware API to complete the backups.
I had a string of issues like this and decided that Veeam was just too flaky and unpredictable so ended up ditching it. I only need to back up a small home lab so now use Aomei Cyber Backup. Definitely not a commercial grade product but for home use it’s simple, doesn’t need “proxies” and reliable. Backs up ESXi VMs no problem and without an agent, so was fine for me.
Hello, unfortunately, I am experiencing the same problem. An error has occurred out of nowhere. I have not been able to solve it for 3 days. What is the exact solution?
[01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies /01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version <01.11.2023 04:33:51.310] <01> Error Task failed. l01.11.2023 04:33:51.310] <01> Error No proxy available (System.Exception)
Based on the errors posted did you check your proxy servers? It seems like there is not a proxy that can communicate with the VMware API to complete the backups.
Hi
There is prosxi that it added when adding vcenter
I also did not add a prosxi.
It has worked like this for 3 years without any problems, but it started giving errors 2 days ago and we could not figure out the reason.
Hello, unfortunately, I am experiencing the same problem. An error has occurred out of nowhere. I have not been able to solve it for 3 days. What is the exact solution?
[01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies >01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version b01.11.2023 04:33:51.310] <01> Error Task failed. e01.11.2023 04:33:51.310] <01> Error No proxy available (System.Exception)
Based on the errors posted did you check your proxy servers? It seems like there is not a proxy that can communicate with the VMware API to complete the backups.
Hi
There is prosxi that it added when adding vcenter
I also did not add a prosxi.
It has worked like this for 3 years without any problems, but it started giving errors 2 days ago and we could not figure out the reason.
What version of Veeam are you using? Did you check the logs to see if there is any other messages to help - C:\ProgramData\Veeam\Backup
Other than that a support case might be needed to further troubleshoot.
Hello, unfortunately, I am experiencing the same problem. An error has occurred out of nowhere. I have not been able to solve it for 3 days. What is the exact solution?
[01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies 01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version r01.11.2023 04:33:51.310] <01> Error Task failed. d01.11.2023 04:33:51.310] <01> Error No proxy available (System.Exception)
Based on the errors posted did you check your proxy servers? It seems like there is not a proxy that can communicate with the VMware API to complete the backups.
Hi
There is prosxi that it added when adding vcenter
I also did not add a prosxi.
It has worked like this for 3 years without any problems, but it started giving errors 2 days ago and we could not figure out the reason.
What version of Veeam are you using? Did you check the logs to see if there is any other messages to help - C:\ProgramData\Veeam\Backup
Other than that a support case might be needed to further troubleshoot.
Hi,
I am using veeam version 12.
Veeam support department could not find a solution
I will try Veeam 9, 10 and 11, I hope it will be fixed.
Hello, unfortunately, I am experiencing the same problem. An error has occurred out of nowhere. I have not been able to solve it for 3 days. What is the exact solution?
[01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies 01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version 01.11.2023 04:33:51.310] <01> Error Task failed. .01.11.2023 04:33:51.310] <01> Error No proxy available (System.Exception)
Based on the errors posted did you check your proxy servers? It seems like there is not a proxy that can communicate with the VMware API to complete the backups.
Hi
There is prosxi that it added when adding vcenter
I also did not add a prosxi.
It has worked like this for 3 years without any problems, but it started giving errors 2 days ago and we could not figure out the reason.
What version of Veeam are you using? Did you check the logs to see if there is any other messages to help - C:\ProgramData\Veeam\Backup
Other than that a support case might be needed to further troubleshoot.
Hi,
I am using veeam version 12.
Veeam support department could not find a solution
I will try Veeam 9, 10 and 11, I hope it will be fixed.
What version of VMware are you using? Might need to think about an upgrade there too. Just looking back at the error and API message. V12 is supposed to support 6.x so may not be an issue at all.
Hello, unfortunately, I am experiencing the same problem. An error has occurred out of nowhere. I have not been able to solve it for 3 days. What is the exact solution?
[01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies 01.11.2023 04:33:51.295] <01> Info ProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version /01.11.2023 04:33:51.310] <01> Error Task failed. <01.11.2023 04:33:51.310] <01> Error No proxy available (System.Exception)
Based on the errors posted did you check your proxy servers? It seems like there is not a proxy that can communicate with the VMware API to complete the backups.
Hi
There is prosxi that it added when adding vcenter
I also did not add a prosxi.
It has worked like this for 3 years without any problems, but it started giving errors 2 days ago and we could not figure out the reason.
What version of Veeam are you using? Did you check the logs to see if there is any other messages to help - C:\ProgramData\Veeam\Backup
Other than that a support case might be needed to further troubleshoot.
Hi,
I am using veeam version 12.
Veeam support department could not find a solution
I will try Veeam 9, 10 and 11, I hope it will be fixed.
What version of VMware are you using? Might need to think about an upgrade there too. Just looking back at the error and API message. V12 is supposed to support 6.x so may not be an issue at all.
hi,
VMware ESXi, 6.7.0, 20497097
hi veeam version 11 I installed it from scratch, there is no problem for 10 hours, I continue to follow it.
hi veeam version 11 I installed it from scratch, there is no problem for 10 hours, I continue to follow it.
Interesting for sure. There has to be some incompatibility somewhere with v12. Keep us posted.
hi veeam version 11 I installed it from scratch, there is no problem for 10 hours, I continue to follow it.
Interesting for sure. There has to be some incompatibility somewhere with v12. Keep us posted.
hi,
5 esxi no problem
We added 1 more server and the problem started again and gave the same error.
It worked for 18 hours without any errors. When I added 1 or 2 servers, the error started again.
The server I added is VMware ESXi, 8.0.2, 22380479
02.11.2023 19:49:18] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies r02.11.2023 19:49:18] <01> Info nProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version P02.11.2023 19:49:18] <01> Error Task failed. 02.11.2023 19:49:18] <01> Error No proxy available (System.Exception)
hi veeam version 11 I installed it from scratch, there is no problem for 10 hours, I continue to follow it.
Interesting for sure. There has to be some incompatibility somewhere with v12. Keep us posted.
hi,
5 esxi no problem
We added 1 more server and the problem started again and gave the same error.
It worked for 18 hours without any errors. When I added 1 or 2 servers, the error started again.
The server I added is VMware ESXi, 8.0.2, 22380479
<02.11.2023 19:49:18] <01> Info ProxyDetector] VMware host API version is V672. Skipping not x64 proxies o02.11.2023 19:49:18] <01> Info nProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version I02.11.2023 19:49:18] <01> Error Task failed. 02.11.2023 19:49:18] <01> Error No proxy available (System.Exception)
Are you on the latest patch for v12? Check here as you need to be for vSphere 8U2 support - https://www.veeam.com/kb4420
