Good day!
We have a requirement to route VMware backup over the dedicated VMkernel network on ESXI hosts. Unfortunately, the CommVault solution does not have a proper method to route VMware backup traffic over 902 (NFC) to HyperscaleX. If I’m correct the “Dedicated Interface Paring (DIP)” will not work for the VMware backup type. Please let me know if there are some improvements made in the latest Version to manage VMware backup traffic using DIP.
Below are the environment details, IP, and names being just dummy, curious to know if it will work if I use a host file entry to route traffic over a dedicated VMkernel network.
Commserve: IP and Name
MGMT -→ 192.168.10.10 cs01.test.com
Backup -→ 10.0.8.10
HyperScaleX: Network label, IP and Name. Three node HSX cluster. Bond1 has sub interfaces.
Bond1.1 → CS-Reg → 192.168.10.11 HSX01.test.com, 192.168.10.12 HSX02.test.com, 192.168.10.12 HSX03.test.com → This has DNS entry.
Bond1.2 → Data Protection 10.0.8.11, 10.0.8.12, 10.0.8.13
Bond2 → Storage Pool network. 192.168.20.10, 192.168.20.11,192.168.20.12
VMware Network: IP and Name
MGMT → 192.168.10.x
VCenter -→ 192.168.10.14 vcenter1.test.com
ESXi -→ 192.168.10.15 ESX01.test.com, 192.168.10.16 ESX02.test.com ---> This has DNS entry.
Dedicated VMkernal Network → ESX01 → 10.0.8.14, ESX02 → 10.0.8.15
I will give a host file entry on HyperScaleX server as follows.
10.0.8.14 ESX01.test.com
10.0.8.15 ESX02.test.com
What I do not know is, the ESX/Vcenter by default will resolve the HyperscaleX to HSX01.test.com 192.168.10.11 so I expect that it will move the traffic from ESX Management network 192.168.10.15 to HyperscaleX 192.168.10.12
In this context how ESXi server will move traffic form ESXi 10.0.8.14 interface to HyperscaleX 10.0.8.11 interface? Please help.