Unable to allocate processing resources. Error: All backup proxies are offline or outdated

Are you integrating into enterprise storage with this?

I had this with a NetApp integration previously whereby some NetApp SVMs were provisioned ‘with’ NFS access, even though at the front end this appeared disabled. Veeam’s integration discovered this NFS ‘mount’ and tried to communicate to it even though the SVM didn’t have an interface Veeam could communicate with it via.

Hi @csaha77 -

So, you're Proxies are offline? Many reasons can cause this. Any recent changes to VBR or the Proxies. Can you ping them from VBR? Check any firewall rules? DNS ok? 

As @coolsport00 said, there are many reasons that can cause.

You also can reference this document to troubleshoot it.

https://www.veeam.com/kb1857

Check the proxy for old components that may be even older than the previous version and remove them from control panel.  Then edit the proxy again in Veeam and see if that works. I have seen leftover components cause this.

@csaha77 I just had this issue and had to completely remove the proxy even from the managed servers section. Uninstall the Veeam components and reboot it then add it back.  That fixes it.

@Chris.Childerhose Tried to remove the proxy from managed server but getting error unable to delete the selected host because it carries one or more backup infrastructure role. Did you remove Veeam components from proxy server? What components did you remove?

Hi @csaha77 -

You have to remove it from being a Proxy first. But be advised, if you have a Backup or Copy job using the Proxy explicitly, you need to change the Job(s) to at least temporarily use ‘Automatic’. Once all the Jobs are changed, rt-click on the Proxy you’re having issue with, then click Remove. After the role is removed from it, you can then remove it as a Managed Server, then re-add per Chris’s instructions.

Yes remove it as a Proxy server first. Then remove from managed servers which will remove Veeam software.  Then add it back as a proxy again but first check the server to ensure all components are gone and if not manually remove them and reboot. Then add back to Veeam as a Proxy.

And if you’re like me, it may still not work well because I have a failing proxy server (or former proxy server) that was also a repo server.  And I can’t remove that repo just yet, so I ended up building a new proxy server (or servers) and removed the proxy role from that server for the time being.

@Chris.Childerhose In the managed servers, the backup server is showing not available and has a red cross besides the servername, when rescan, host discovery failed with error access denied, RPC call. When trying to delete from Backup Proxy, error Unable to delete the selected proxy because it carries additional backup infrastructure roles

You need to remove the roles for the Proxy in the Backup Proxy section first - anywhere you see the Proxy - VMware, Agent, CDP -- remove here first. Then go to Managed Servers and remove the server at that point.  Then log in to the server and ensure no more Veeam components are left and reboot.

After that you can add it back to the Proxy Server section to install the roles again.  Not much else I can tell you here just following these steps works.

Even with the X on the server you can remove it but first remove from the Proxy Servers section.

ok went to the Backup proxies and when trying to delete error Unable to delete the selected proxy because it carries additional backup infrastructure roles

And what does the other roles state?  If this is the main VBR server then you will not be able to remove it from here.  If it is a separate Proxy then you can.  Sounds like you have an all-in-one install so you cannot remove it.  Unless I am wrong but just need to do a little more reading on how Veeam works.

A screenshot of the Backup Proxy section of the tree would be very helpful.

This is from backup Proxies.

This is from Managed servers

“So, my guess is the Proxy you are trying to remove is also the VBR server which contains other roles.” ← Yep..that’s what it kinda looks like to me, too.

@Chris.Childerhose @coolsport00 Thanks for your support will look into this issue again next week

Sounds good...keep us posted @csaha77 

Not a problem.  Keep us posted on how you progress and what solves the issue.

Recreated Backup with Automatic selection, rescan backup proxy and check credentials for vcenter servers.

Great glad to hear you got it working.  Thanks for posting what helped fix it.

Glad you got it sorted.