I need some help working out what I am doing wrong here, I'm hoping that I am just missing something obvious, but for the life of me my brain is a little bit too frazzled at the moment and if anyone could give me a hand it would be massively appreciated.
The goal: Use Veeam Backup & Replication to backup VMs located on two seperate vSphere 6 farms with dedicated storage over fibre channel.
vSphere Farm 1 is 5x HP DL380 G9 servers, all with HPE 82Q 8Gb Dual Port PC HBA's. They connect to a HP 8/8 Base 8-port enabled B-Series SAN switch. This then connects to the storage which is a HP MSA 2042 with 8Gb SW B-Series SFP+
vSphere Farm 2 is 3x HP DL380 G8 servers all with HPE 82Q 8Gb Dual Port PC HBA's. They connect directly to a HP MSA 2040 over FC, again with 8Gb SFP's.
The Veeam server is a physical HPDL380 G9 server, running Windows Server 2012R2 with two seperate HPE 82Q 8Gb Dual-Port FC HBA's installed. Two ports on one of the FC HBA's connects directly to the MSA 2040 for Farm 2. The other FC HBA 2 ports connect into the B-Series SAN switch.
The problem - the Veeam is backing up Farm 2 perfectly without issue, displaying [san] as direct access. Farm two however is failing with direct SAN access, and is falling back on [ndb], which is obviously slower.
I have been on to the MSA 2042 in Farm 1 and made sure the initiators are mapped to the datastores correctly just like on the other cluster.
I have been wondering if it is something to do with MPIO on the Veeam server not being setup correctly, however I have followed the HP guides, so I am unsure.
Is anyone able to spot what is wrong here... i've scoured HP's documentation library for days, reading about 15 different PDF's trying to understand this, but I am failing to see the issue.
Again any help would be greatly appreciated.