Hello @Comtech
From a Hyperscale perspective there is no limitation on the Hyperscale that wouldn’t allow this to work. SAN does support iSCSI but it would depend on how its configured (hopefully one of our Client Engineer’s could provide more information here). Regarding the network, the backup would use the Data Protection network on the Hyperscale unless a DIP was put in place to force traffic over a specific network.
Configuring a Dedicated Backup Network Using Data Interface Pairs - https://documentation.commvault.com/2023e/expert/7140_configuring_dedicated_backup_network_using_data_interface_pairs.html
Thank you,
Collin
@Comtech Take a look at the following documentation and see which fits best for your environment.
https://documentation.commvault.com/2023e/expert/36340_transport_modes_for_vmware.html
It seems maybe you are looking to do hotadd?
Hi Collin, Thanks for your response. Let me raise a case with support and check further for ISCSI SAN mode backup.
Besides this, we too have a plan to do backup using dedicated VMkernel network on ESXI hosts. Unfortunately, the CommVault solution do 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 know if there are some improvements made in the latest Version to manage VMware backup traffic using DIP.
Below is the environment details IP and names being just dummy, curious to know will it work if I use host file entry to route traffic over dedicated VMkernel network.
Commserve:
MGMT -→ 192.168.10.10 cs01.test.com
Backup -→ 10.0.8.10
HyperScaleX
Bond0.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.
Bond0.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:
MGMT → 192.168.10.x
Dedicated VMkernal Network → ESX01 → 10.0.8.14, ESX02 → 10.0.8.15
VCenter -→ 192.168.10.14
ESXi -→ 192.168.10.15 ESX01.test.com, 192.168.10.16 ESX02.test.com ---> This has DNS entry.
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.
Hello @Comtech
The DIP will only affect Commvault traffic at the application level. If you want VMWare\ESXi traffic to route over specific networks you would need to do this at the network level, If I am understanding you correctly.
Thank you,
Collin