Currently we have our vSphere cluster's VMkernel management adapters configured on VLAN100.
Our vCenter server is on VLAN200 (with distributed virtual switch capability, in case that matters here).
Our Veeam B&R server is on VLAN300 and is connected to the vSphere cluster via vCenter.
To achieve that backup traffic won't get routed, we would like to add an additonal VMkernel management apapter on VLAN 300 to the vSphere cluster.
If possible we would like to NOT add the additional VMkernel ports on VLAN300 to our internal DNS server but adding them to the hostfile would be a solution.
Now the question is: Without blocking the traffic on firewall side, how can we make sure that Veeam B&R is forced to always take the network path on VLAN300 for backup traffic?
Thank you in advance!
-
- Enthusiast
- Posts: 40
- Liked: 4 times
- Joined: Apr 08, 2016 6:20 am
- Contact:
-
- Veeam Software
- Posts: 78
- Liked: 48 times
- Joined: Feb 19, 2019 3:08 pm
- Full Name: Andy Sturniolo
- Contact:
Re: Force backup network traffic path on multiple VMkernel management adapters
Hi there…
Yes this is possible.. to start, have a look at our documentation on Specifying Preferred Networks… https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Here is a way you could approach this:
Add VMkernel Adapters on VLAN300:
In vSphere Web Client, navigate to the host, go to Configure > VMkernel adapters, and add a new adapter on VLAN300.
Update Hostfile(DNS is preferred)
Edit C:\Windows\System32\drivers\etc\hosts on the Veeam B&R server to map ESXi hostnames to their VLAN300 IPs.
Configure Veeam B&R Preferred Networks:
In Veeam B&R, go to Backup Infrastructure > Managed Servers, right-click the ESXi hosts, select Properties, and set VLAN300 IPs as the preferred network for backup traffic.
Verify Routing
Ensure routing tables on Veeam B&R server and ESXi hosts direct backup traffic through VLAN300.
Yes this is possible.. to start, have a look at our documentation on Specifying Preferred Networks… https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Here is a way you could approach this:
Add VMkernel Adapters on VLAN300:
In vSphere Web Client, navigate to the host, go to Configure > VMkernel adapters, and add a new adapter on VLAN300.
Update Hostfile(DNS is preferred)
Edit C:\Windows\System32\drivers\etc\hosts on the Veeam B&R server to map ESXi hostnames to their VLAN300 IPs.
Configure Veeam B&R Preferred Networks:
In Veeam B&R, go to Backup Infrastructure > Managed Servers, right-click the ESXi hosts, select Properties, and set VLAN300 IPs as the preferred network for backup traffic.
Verify Routing
Ensure routing tables on Veeam B&R server and ESXi hosts direct backup traffic through VLAN300.
-
- Enthusiast
- Posts: 40
- Liked: 4 times
- Joined: Apr 08, 2016 6:20 am
- Contact:
Re: Force backup network traffic path on multiple VMkernel management adapters
Just for completion:
I did not find the specific setting mentioned above, right-clicking on the ESXi-Host does not provide the accorindg setting to configure a specific network for preferred backup-traffic:
Configure Veeam B&R Preferred Networks:
In Veeam B&R, go to Backup Infrastructure > Managed Servers, right-click the ESXi hosts, select Properties, and set VLAN300 IPs as the preferred network for backup traffic.
Instead I found it here:
Main menu --> Network traffic rules --> Networks...
Cheers!
I did not find the specific setting mentioned above, right-clicking on the ESXi-Host does not provide the accorindg setting to configure a specific network for preferred backup-traffic:
Configure Veeam B&R Preferred Networks:
In Veeam B&R, go to Backup Infrastructure > Managed Servers, right-click the ESXi hosts, select Properties, and set VLAN300 IPs as the preferred network for backup traffic.
Instead I found it here:
Main menu --> Network traffic rules --> Networks...
Cheers!
Who is online
Users browsing this forum: Google [Bot] and 51 guests