I just had a nice call with the Veeam Support regarding a problem I ran into after activating the "EnableSameHostDirectNFSMode" Registry parameter (value:"2") that was implemented with 9.5U3:
Queued for processing at 12.04.2018 22:53:08
Required backup infrastructure resources have been assigned
VM processing started at 12.04.2018 22:53:14
VM size: 80,0 GB (39,6 GB used)
Storage initialized 00:18
Getting VM info from vSphere 00:00
Error: Index was outside the bounds of the array.
Network traffic verification detected no corrupted blocks
Processing finished with errors at 12.04.2018 22:55:10
The solution was very simple: I forgot that I set a proxy restriction on the backup job (long ago). Since the value "2" forces Veeam to only use backup proxies on the same host as the VM, but the job was restricted to a different set of proxies, the backup failed.
Could you please catch this configuration error with a meaningful error message? This would have saved me a lot of troubleshooting. My suggestion:
"No Backup Proxy available due to restriction on the Backup Job" (or something similar)