In customer environment there is a network separation in place. There are 3 VLANs
1) VLAN1 - vcenter / esxi host management
2) VLAN2 - MediaAgent / backup network
3) VLAN3 - NFS storage network
ESXi hosts are configured in VLAN1 (management network) and VLAN3 (NFS storage network)
MediaAgent is configured in VLAN2 and VLAN3 (NFS transport mode)
This works great for backups and restores, but since VLAN3 is not routed a LiveMount feature does not work - an ESXi host can't mount NFS from MediaAgent. AFAIK that is because since VLAN3 is the storage network, ESXi host will try to mount NFS using that network. Unfortunately it cannot reach main MediaAgent NIC in VLAN2 (that is a network interface that MA hostname is resolved to). Switching to MA NIC in VLAN3 is also not the answer since it is not routed and can't reach ESXi host management in VLAN1. Since it is a Commvault ↔ VMware traffic DIPs also cannot be used.
A solution could be if there is a way to tell Commvault software which MA IP address should be used to mount NFS. There are some Additional settings for different ports usage (nMount3Port, nNfs3Port) but I can't find anything that would allow me to specify an IP address that should be used for NFS mounts during LiveMount.
Can anyone suggest how to cope with such setup or if maybe there is undocumented Additional Settings like “nMount3Address” that would solve my issue nice and easy?
Best answer by Robert HorowskiView original