Hi StorageMatt and Jbs727,
In regards to using Data Server IP, you will be leveraging application level (Commvault) to export via 3ndfs (using nfs) to allow access between a locally mounted volume on one MediaAgent to another MediaAgent (when using Block Device).
However in saying that, this is not fully High-availability, as you will still rely on the single MediaAgent with Block access to be online to allow exports to be made to another MediaAgent. If the primary MediaAgent is offline you will lose access to the Mount Path.
- Side Note - if you are able to configure Clustered Storage (e.g. Windows Clustering) that will allow you to achieve HA outside of Commvault, which will translate to HA at Application level.
If you are able to configure exports of CIFs or NFS at Storage Level and create the Disk Library (within Commvault) you will be able to leverage better HA (Note - however you will be using IP, instead of iSCSI or FC - so performance might not be the best).
Additional note - with 3dnfs (since you are leveraging nfs), this works at a different layer from Data Server IP, that is why it is not compatible.