Skip to main content
  • EN

Someone on the Community reported the error of this post - “All backup proxies are offline or outdated” here -

https://community.veeam.com/topic/show?tid=6645&fid=66

I ran in to this issue in my HomeLab and opened a ticket with Veeam Support about it.  I was able to figure out the issue myself and wanted to post the fix steps here so that if you run in to this issue you can take the steps needed to address it yourself.

This error does not seem to report anything in the log files which was the first thing I checked.  So, the steps to fix it are as follows -

  1. Remove the Proxy from the Veeam console using Delete.
  2. Remove the server from Managed Servers section - this will uninstall the components from the server.
  3. Log in to the Proxy server to ensure all components for Veeam are gone - if not remove them in the Control Panel
  4. Reboot the Proxy server
  5. Add the server back in to the Veeam Console as a Proxy server which will reinstall the components again.
  6. Validate your failed jobs by running them again and this time when it uses the Proxy it will work, and the job will complete successfully.

I had 5 jobs which were NAS File backups that failed but after doing this they ran successfully on schedule.

Something with the component files was corrupted somehow as validated by the Support Rep as well so removing and readding it to Veeam addresses the issue.

Hopefully this helps those that run in to this issue to resolve it themselves without the need for a Support case (closing mine today 😁)

Easy fix, but annoying error I’m sure. Thanks for sharing how Support got you working again Chris!

Not a problem.  Sharing is caring as they say. 😉

Also, support did not fix it I did as that tends to happen when I open cases and can teach them the fix.  🤣

“Also, support did not fix it I did as that tends to happen when I open cases and can teach them the fix.  🤣” ← Nice! hahaha

Thanks for posting the fix. I’m cautious with my proxies as they are also my repos. (Hope to separate soon on our hardware refresh). 

That’s a little game I play when I open tickets to. Open the ticket, then see if I can fix it before I get a response. 🤣.  I can usually fix a VMware issue by the time I get a response. 

 

Yeah...with the quality of VMW support, you're better off trying to resolve an issue on your own 😏

I can almost always fix things myself with Veeam before support gets to it or gives me things to try.  I don’t create the VMW cases here but could probably solve those too.  😋

Thanks for posting the fix. I’m cautious with my proxies as they are also my repos. (Hope to separate soon on our hardware refresh). 

That’s a little game I play when I open tickets to. Open the ticket, then see if I can fix it before I get a response. 🤣.  I can usually fix a VMware issue by the time I get a response. 

 

Not a problem.  It was perplexing as I could watch the jobs run, the proxy goes offline, job fail then the proxy come back online in the Veeam console.  It was strange to say the least.

I just had this same error, i only have 1 backup proxy and use it for all jobs, last night half of the VM’s backed up (all the ones on one VM host) and half of them didn’t (all the ones on a second VM host).

All i did to resolve the issue was in VBR go to “Backup infrastructure”, then “backup proxies”, then right click and select “properties” of each proxy component (ie VMWARE, CDP, Agent) and click “finish” in each properties window so it re-detects everything.

I just had this same error, i only have 1 backup proxy and use it for all jobs, last night half of the VM’s backed up (all the ones on one VM host) and half of them didn’t (all the ones on a second VM host).

All i did to resolve the issue was in VBR go to “Backup infrastructure”, then “backup proxies”, then right click and select “properties” of each proxy component (ie VMWARE, CDP, Agent) and click “finish” in each properties window so it re-detects everything.

Yes this does fix that too. I had to do this during domain migrations.

Hi Chris, your solution is still working. :))) Thank you so much.  

My Problem : 

I was defined proxy name to IP address.  After I was must changed proxy server name  IP to FQDN . I changed all proxy name FQDN than old and new backup job did not working. Because I got an error "All backup proxies are offline or outdated" . I found your solution. Thanks you so much. 

Hi Chris, your solution is still working. :))) Thank you so much.  

My Problem : 

I was defined proxy name to IP address.  After I was must changed proxy server name  IP to FQDN . I changed all proxy name FQDN than old and new backup job did not working. Because I got an error "All backup proxies are offline or outdated" . I found your solution. Thanks you so much. 

Glad it helped you out. 👍

Hi Chris, your solution is still working. :))) Thank you so much.  

My Problem : 

I was defined proxy name to IP address.  After I was must changed proxy server name  IP to FQDN . I changed all proxy name FQDN than old and new backup job did not working. Because I got an error "All backup proxies are offline or outdated" . I found your solution. Thanks you so much. 

Glad it helped you out. 👍

You're good at this, man. 💪

I just had this after upgrading to Veeam 12.2.0.334.  All Backups started failing.  I could get things going again breifly by checking the proxy properties as per R2D2’s suggestion, - I could backup 1 vm OK then the full job would start failing again.   Eventually turned out to be a coincidence where we were running ESET Antivirus.  It had enabled its Network botnet protection mechanism and was blocking veeam traffic between the B&R and the proxies after a small amount of traffic had made it through.   Hence establishing a new job backing up 1 small vm would work, but running the original main job with multiple vm’s would fail 100% of the time. Most frustrating and difficult to track down when not suspecting a Man in middle intercepting “some” traffic and then blocking all.  I removed and upgraded the proxy several times before finding it. Im not sure why the ESET change happened at the same time - suspect it was a new default policy they pushed.  I hate AV managing network traffic.  grrrr

I faced this problem today, started Veeam Mount service then fixed it.

Comment


Terms & Conditions