Skip to main content
  • EN

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.

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
x02.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
02.11.2023 19:49:18] <01> Error        Task failed.
T02.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

 

 

Before that, we need to check whether it is vSphere 8 or not, so I removed all vSphere 8 from the system.
there is only 6.7

I will continue testing this way.

Hİ

 

No problems for 17 hours, it takes backups without any problems.
I only have vSphere 6.7

The problem is that VMware ESXi, 8.0.2, 22380479 cannot take a backup in this version after a while.

 

 

https://www.veeam.com/kb4420

Published: 2023-03-07
Last Modified: 2023-08-03

https://docs.vmware.com/en/VMware-vSphere/8.0/rn/vsphere-esxi-802-release-notes/index.html

VMware ESXi 8.0 Update 2 | 21 SEP 2023 | GA ISO Build 22380479

So kb4420 update does not support VMware ESXi 8.0 Update 2. briefly.

 

because VMware ESXi 8.0 Update 2 was released on 21 SEP 2023

 

KB4420 was updated in August. The problem appears immediately, but after a while, I think that's why there is still no news about it.

 

Veeam urgently needs to do research and update its APIs.
Because VMware ESXi 8.0 Update 2 new APIs have arrived. Because of that error, Prox shuts down after 5-6 hours.
   rProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version.

hi

 

https://forums.veeam.com/vmware-vsphere-f24/vmsa-2023-0023-cvssv3-base-score-of-9-8-and-update-2-support-t90606.html#p501812

 



Our upcoming version 12.1 will support vSphere 8.0 U2. We plan to release v12.1 before the end of this year.
If you want to keep your environment fully supported with Veeam, I recommend to install patches for vSphere 8.0 U1 for now.

 

Veeam 12.0 no support vSphere 8.0 U2.

Veeam 12.1 yes support :)

 

 

hi

 

https://forums.veeam.com/vmware-vsphere-f24/vmsa-2023-0023-cvssv3-base-score-of-9-8-and-update-2-support-t90606.html#p501812

 



Our upcoming version 12.1 will support vSphere 8.0 U2. We plan to release v12.1 before the end of this year.
If you want to keep your environment fully supported with Veeam, I recommend to install patches for vSphere 8.0 U1 for now.

 

Veeam 12.0 no support vSphere 8.0 U2.

Veeam 12.1 yes support :)

 

 

The latest patch for v12.0 was certified to support 8.0U2 as I use it at home with no problems.

12.1 will for sure support it.

hi

 

https://forums.veeam.com/vmware-vsphere-f24/vmsa-2023-0023-cvssv3-base-score-of-9-8-and-update-2-support-t90606.html#p501812

 



Our upcoming version 12.1 will support vSphere 8.0 U2. We plan to release v12.1 before the end of this year.
If you want to keep your environment fully supported with Veeam, I recommend to install patches for vSphere 8.0 U1 for now.

 

Veeam 12.0 no support vSphere 8.0 U2.

Veeam 12.1 yes support :)

 

 

The latest patch for v12.0 was certified to support 8.0U2 as I use it at home with no problems.

12.1 will for sure support it.

 

The problem is that the vm version is 21 and the new operating system is not supported. The patch was released before vSphere 8.0 U2 was released, so support is simply not available.
I tested many times and the result did not change.

 

blem is that the hardware version is 21, so downgrading it to hardware version 20 eliminates the problem. months?
Is it kain now?

https://docs.vmware.com/en/VMware-vSphere/8.0/rn/vsphere-esxi-802-release-notes/index.html

21 SEP 2023 

Is there more than 2 months between? How will Veeam patch a version that will be released in 2

 

The pro

 

See the published version patch date.

 

 

 

 

Published: 2023-03-07
Last Modified:

2023-08-03

 

 

 

In fact, our QA has just finished the regression testing of version 12.0.0.1420 P20230718 (latest) against vSphere 8.0 U2 and we're ready to declare compatibility-level support. "Compatibility-level" means no support for new features like virtual hardware version 21 or new vSAN ESA features. In other words, you can upgrade to vSphere 8.0 U2 but you cannot leverage any U2-specific functionality at this time. It will be supported in 12.1 only.

The related support KB article should be updated shortly, I'm writing this a split second after receiving the announcement from QA and remembering seeing this thread earlier today 

 

 

 

 

 

Comment


Terms & Conditions