tsightler wrote:The behavior is expected. NBD mode is used to backup a VM only if there is no proxy selected in the job that can backup that VM using one of the other transport modes. Otherwise, Veeam will wait for the proxy with either hotadd or Direct SAN access to the datastore to become available.
My understanding is that this was implemented mainly due to the fact that, when using NBD transport, technically ANY proxy can backup all VMs in the entire infrastructure, which definitely might not be a good thing. If I have a configuration with 2 sites, I don't want the proxy at Site 2 using NBD mode to backup VMs at Site 1, but there's no way for Veeam to know where that physical proxy lives, it could be anywhere in the world. Sure, we could make some assumptions about layer-2 adjacency, and we do check some of that, but even then what we can assume this is quite limited as it wouldn't work in cases of stretched layer-2.
Users browsing this forum: tsightler and 32 guests