Problems with Veeam

vooze

Well-Known Member
May 11, 2017
81
21
48
36
Denmark
vooze.dk
Hi!

For about 10 days it was working fine, then today after importing about 8 VMs from VMware ESXI (supported Proxmox function) now Veeam can't index the Proxmox host no matter what I try.
I get this message:

Successfully validated the connection
Successfully updated the server
Failed to refresh entities



:(

The funny thing is I can even deploy a Proxmox Worker / Proxy from Veeam, so Veeam clearly has connection to Proxmox but it just won't index it for some reason.

I even tried reinstalling Veeam on a new VM, Restarting the Proxmox host (running 8.3 newest), add by IP/host. Proxmox and Veeam is on same VLAN so no firewall in between.

PVE logs:
Nov 28 21:20:20 pve01 systemd[1]: Started session-905.scope - Session 905 of User root.
Nov 28 21:20:20 pve01 sshd[116895]: pam_env(sshd:session): deprecated reading of user environment enabled
Nov 28 21:20:20 pve01 sshd[116895]: Received disconnect from 10.1.2.120 port 64683:11: Connection terminated by the client.
Nov 28 21:20:20 pve01 sshd[116895]: Disconnected from user root 10.1.2.120 port 64683
Nov 28 21:20:20 pve01 sshd[116895]: pam_unix(sshd:session): session closed for user root

I have found a guy with simular issues here (In german, I had to use translate) but he had exact same issue: https://forum.proxmox.com/threads/fehlermeldung-veeam-verbindungsaufbau-zu-proxmox.154286/

We are stuck here, and unable to backup about 25 production VMs. Please help!
 
Perhaps you will share your experience dealing with Veeam support? that would be valuable to this forum. I'm assuming you're posting here because you did not get resolution that way.
I actually just posted to Veeam support as well. Just posting here as well hoping more people have this problems and get some faster help, but will deninitly keep you updated :)
 
Im a little bit surprised, because is Veeam for Proxmox already stable. I thought its in an experimental state and therefor not for production environments.
 
Last edited:
Just a shot in the dark here, but I recall having issues when we first implemented Veeam with Proxmox we were having similar issues with refreshing stand-alone (ie non-clustered) PVE servers. I was asked by Veeam support to confirm I had the dmidecode package installed (it was not). After installing it was able to gather host information properly. To check if you have that package installed you can run:

dpkg -l | grep dmidecode
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!