- Posts: 162
- Liked: 17 times
- Joined: Mar 13, 2019 2:30 pm
- Full Name: Alabaster McJenkins
vm managmenet network 10.1.5.0/24
vm production network 10.1.10.0/24
network management vlan 10.1.2.0/24
does it matter much which network Veeam B&R (main server, proxy role, everything etc) is on so long as it can talk to anything via routing etc? Or would you suggest even creating a new vlan just for the backup server itself...?
- Posts: 450
- Liked: 93 times
- Joined: Dec 08, 2014 2:58 pm
- Full Name: Steve Krause
Veeam Certified Architect
- Veeam Software
- Posts: 374
- Liked: 79 times
- Joined: Aug 02, 2011 1:06 pm
- Full Name: Joe Gremillion
- Location: Dallas, TX USA
The backup repository can go on a different VLAN like a backup vlan if there is a need to keep the backup traffic separate from the management VLAN.
If the repository gets put in a separate VLAN (like a backup network) from the proxy then it helps if there are two nics in the proxy - one on the management vlan, and one on the backup network.
In the network options menu in the VBR server, you can set the preferred network to be the network address of the backup network.
NA Core Solutions Architect - Central region
- Veeam Software
- Posts: 4227
- Liked: 778 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
Veeam gets from vCenter the full qualified domain name of the ESXi host, then ask DNS system to get the IP. You can manipulate this to use a specific interface (vmkernel IP) by manipulating DNS on Veeam B&R Server and all Proxies used. The most simplest was is by using the hosts file.
Please see full explanation and examples here: https://bp.veeam.expert/dns_resolution
Users browsing this forum: Google [Bot] and 41 guests