I have production systems on a FC SAN (no iSCSI) which is mapped to our ESX environment, I haven't been able to persuade the organisation to add an iSCSI controller to our SAN.
Unable to get permission for an additional mapping to the on-site veeam proxy from the HBA, with our SAN requiring an update to allow NVIP mapping to proxy vm.
Just wondered if adding the individual vmdk as an additional hard disk to the veeam proxy, would allow SAN mode for the job?
Veeam job fails with access error as I understand it requires access to the LUN hosting the vmdk, I can see the volumes un-mounted on the proxy as expected, so thinking someone may have an idea if there's a workaround.
Thank you very much for your time