Nope. Jobs still failing.
I have a second site with a single Hyper-V host (Windows Server 2012) and a similar repository. The Veeam server is actually the repository for this site. This site has no issues at all. I even exported all VMs from an older host (Windows Server 2008 R2) to the new one and didn't upgrade the Hyper-V integration components, and it still completed all jobs successfully.
As another test, I connected a cheapo WD MyCloud single hard drive "NAS" and added it as a CIFS repository. VMs that fail normally, still fail. VMs that succeed, succeed here too.
Does anyone know what the actual error means? Could it be a networking issue, independent of Veeam? If so, why aren't all jobs failing? I can reliably backup 2 VMs with no problems, but all the others are failing.
Frustrating. . .