• EN
Solved

Backup fails, no proxy available

D
Userlevel 2

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:

[ProxyDetector] VMware host API version is V800. Skipping not x64 proxies
[ProxyDetector] 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.

icon

Best answer by coolsport00 2 September 2023, 18:07

View original

30 comments

U
Userlevel 2

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 

 

 

 

 

 

Chris.Childerhose
Userlevel 7
Badge +20

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.

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
U
Userlevel 2

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 :)

 

 

U
Userlevel 2

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.
   [ProxyDetector] VMware host API version is V672 and all available proxies are not x64 so we can not use it with such API version.

U
Userlevel 2

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
[02.11.2023 19:49:18] <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
[02.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

 

 

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.

Chris.Childerhose
Userlevel 7
Badge +20

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
[02.11.2023 19:49:18] <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
[02.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

 

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
U
Userlevel 2

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
[02.11.2023 19:49:18] <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
[02.11.2023 19:49:18] <01> Error        Task failed.
[02.11.2023 19:49:18] <01> Error        No proxy available (System.Exception)

Chris.Childerhose
Userlevel 7
Badge +20

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.

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
U
Userlevel 2

hi veeam version 11 I installed it from scratch, there is no problem for 10 hours, I continue to follow it.

U
Userlevel 2

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

Chris.Childerhose
Userlevel 7
Badge +20

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.

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
U
Userlevel 2

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.

Chris.Childerhose
Userlevel 7
Badge +20

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.

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
U
Userlevel 2

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.

D
Userlevel 2

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.

Chris.Childerhose
Userlevel 7
Badge +20

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.

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
U
Userlevel 2

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)

 

 

dips
Userlevel 7
Badge +7

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.

Dipen N. K. | IT Security Specialist | Veeam Legend 2022 - 2023 | www.dipen.co.uk
D
Userlevel 2

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….. 🤔

coolsport00
Userlevel 7
Badge +17

Follow the User Guide for more info if needed.

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
coolsport00
Userlevel 7
Badge +17

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.

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
D
Userlevel 2

@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!! 😀

coolsport00
Userlevel 7
Badge +17

That’s a good catch Mark! Could very well be that.

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
MarkBoothman
Userlevel 7
Badge +6

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.

 

https://helpcenter.veeam.com/docs/backup/vsphere/platform_support.html?ver=120

VMCA2022 | VMCE2021 | Veeam Legend | Twitter: @Boothy71
coolsport00
Userlevel 7
Badge +17

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.

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00

Comment


Terms & Conditions