vmware-vsphere-f24/linux-backup-proxy-m ... 81187.html
... I was going to add this comment there, but the above post was moreso about how multipath does/doesn't work when using iSCSI with Linux and configured for DirectSAN mode, and not really about how to configure it. So I created this post.
That is a FANTASTIC thread btw! Really appreciate all the input shared, especially by @hannesk and @arturE for their PM/QA input.
I'm looking for definitive and supported configuration for Linux to use Direct SAN (Storage) and BfSS. I'm looking to implement Ubuntu Linux as Proxies in my newly-created VBR environment using iSCSI. The User Guide has about 0 guidance on how to get this done for DirectSAN (Storage). Sure, there are some requirements and limitations noted in a few spots, but the actual Linux configuration isn't there. I was mostly going to implement for BfSS on Linux as I have in my current/old environment (but currently use Winodws). But, I was still very curious how to configure a Linux server & Nimble to use DirectSAN as there's no doc anywhere how to do this. Honestly, there isn't one for Windows either. Anyway, I kinda wanted to see which method on Linux, BfSS or DirectSAN, would perform better. When I configured Windows 5-6yrs ago or so, I had to find a few blog posts on the Web on how to configure Windows to use DirectSAN/BfSS. Would be nice to have a supported Veeam document on how to configure BfSS & DirectSAN on both Windows and Linux. I understand with Linux there are different distributions (thus, some difference in pkg names and pkg managers), and there are many storage vendors (with different configurations), but the explicit/detailed configurations for each storage vendor doesn't have to be explicitly detailed and can instead be from a high-level (i.e. "configure your storage Volumes/LUNs to do xyz", etc).
My main question for DirectSAN is 1. how do I configure the VM prod array? And, in my case, I have a Nimble. Specifically, what Access (aside from Linux server IQN) do I give each datastore Volume? My guess is I configure the Linux server access to use both "Volume & Snapshot"? For BfSS you only need to configure "Snapshot". I tested BfSS with the "Snapshot" access and that works; and it does appear multipathing works as well. On the Linux server, for DirectSAN do I just run a 'target discover' cmd only as is needed for BfSS, or do I also need to perform a target "login" operation? Also, Hannes, in the above thread, said DirectSAN isn't really supported with physical Linux servers? Or, maybe more specifically...multipathing? Should that be added in the User Guide? Or, referenced in a KB and linked to from the User Guide? I think that's kind of a big deal IMO.
And all this may even be for naught. Maybe I don't need to implement the complexity of a phys Linux server with iSCSI connection to my SAN? Just thought I'd get better performance than Windows BfSS, as well as a little less maintenance overhead and probably a bit better security footprint than Windows? Maybe using Linux VM Proxies (i.e. hotadd) are good enough? I understand which to use will warrant the good old "it depends on your environment" statement.

Just looking 1. for Linux config info for DirectSAN; any other thoughts I may be missing.
Thanks!