by chris.collins » Thu Jun 02, 2016 3:33 pm people like this post
We had the same issue - restarting the management agent on the host where the VM was housed resolved the issue (this only causes the host to be disconnected from vCenter for a minute or two but doesn't cause any downtime to the other VMs)
Backups have been fine since (2 days and counting)
by Ice-Dog » Mon Jun 06, 2016 8:12 am 1 person likes this post
This has happened to me about 4-5 times since orginally posting. I have narrowed it down to 4 of my 14 hosts that this happens to repeatedly.
I contact my account manager at Veeam to put some weight on this - but the support answers where still poor and not escalated to a the top tier.. "try using another proxy", "try using hot-add". When I am using new transport servers and using hot-add and NFS v3 causes up to 60 sec stun time.
I dragged VMware on a call and the support guy form them was at first very adamant that this could never be a VMware issue if Veeam is able to contact the API to issue snapshot commands and rejected taking any look at my vSphere settings. However I sent them logs from the latest hosts that failed and vCenter with accurate details of the times when the backups error-ed.
They VMware actually came back to me with a possible solution. They see nothing being is being logged about the backups as the backups API is not reaching the ESXi. They think that maybe during a patch that the VDDK may not have installed correctly. Meaning the API calls are not being received.
To attempt to fix this can I will update the host to the latest build. By doing this it will install a fresh VDDK that should allow the API calls in.
I will update once that is completed and report 3 months down the line if the issue will have cropped up again.
by StefanSpecht » Tue Jun 07, 2016 9:19 am people like this post
Same here. Some of our VMWare hosts randomly get this issue. Restarting the management agents is fixing it temporarly, but this happens every few days. We are running Veeam 8 latest update and ESXi 5.5.0 3568722. Only sites that use network mode are affected and espacially those with a lot of VMs on it (= a lot of network traffic) I suspect this to be a bug somewhere in the ESXi network stack (full buffers etc?) and will open a VMWare support case in the next days.
by rayzhang » Mon Jun 13, 2016 1:35 am people like this post
Thanks for your discussions, Now I sloved the same problem like that. I found the vms of veeam failure in a same host ，so I thought maybe is the host problem . Because my hosts had HA，so I migrated the veeam vms to the other host ,and then veeam is backup successfully . I don't know why .Maybe the host need to reboot . I will choose a good time to test if it done .
If your host in HA, you can try to slove it by migration too
by mgratla » Mon Jun 13, 2016 4:34 pm people like this post
pidthepiper wrote: Could you explain this a bit more?
If left unchecked, after about 48 hours of receiving VDDK failures consistently through Veeam (We backup almost 400 machines and they all retry three times) - We see the host loose connection in vCenter momentarily and come back up. From what I've been able to tell, the host self restarted it's vpxa and vpxd processes. After this happens the jobs run fine for a while
by pidthepiper » Mon Jun 13, 2016 4:48 pm people like this post
Ahhh now that is interesting, so eventually the host sorts itself out, but it takes a few days heh. There has to be something that triggers, but neither Veeam or VMware seem to know. Both Support teams are acting like it s the first time they have heard of this issue, even though I point them to this thread, showing peoples support case numbers