Hi @bravo444 -

Have you opened a case with Veeam Support? Probably best to work with then. 

Logs are located at:

C:\ProgramData\Veeam\Backup 

hi @bravo444 

Could I suggest that the correct path for proxmox logs is C:\ProgramData\Veeam\Backup\Plugins\PVE

After this have you tried stopping or open firewall for ALL? This permit to isolated if it’s a network issue… 

Hi Andanet,

I tried to be disabled firewall and also stopped antivirus application.

But the issue still exist.  What is the port number for this phase?  I mean, the port should connect to an appliance.  

Thank you!

You can check all used ports here

https://helpcenter.veeam.com/docs/vbproxmoxve/userguide/used_ports.html?ver=1

Hello.

I checked documents and I tried to opened all necessary ports.  But I still have no luck.

The best way will be to open the case right?  Since I have used community edition, then the respose is very slow.  I know this has no choice…  

In addition, Veeam backup is running on the Proxmox VE host.  I think this should be no problem.

I used Veeam back for ESXi before and the Veem run on ESXi host and it worked without any issue.

Well, the architecture between ESXi and Proxmox for Veeam backup should be the different though..

Hello 

have you checked Proxmox system requirements are satisfied?

https://helpcenter.veeam.com/docs/vbproxmoxve/userguide/system_requirements.html?ver=1

IN Veeam Forum I found this article with same error: 

https://forums.veeam.com/kvm-rhv-olkm-proxmox-f62/trying-to-deploy-veeam-proxmox-workers-getting-errors-during-test-t95254.html

where speaking about a 10006 port not documented. 

Please let us know! 

Hi Andanet,

Thank you so much for your information!  I tried to open 10006 port on router, but the issue has not been fixed.  I still got the same error like Failed to connect to the backup appliance.

I am really not sure what the appliance is in this case.  I am wondering what the port number is for an appliance connection.

Regards,

Hello All,

Good news!  Finally, I found the root cause and worker was tested successfully!

I apologize that I forgot to restart named service after I added worker hostname in DNS.

After rebooting, the issue was fixed.

I would like to thank you so much for your quick help and resopond!

Regards,

estou com o mesmo problema, como resolveu?

agradeço