Hi everyone
we have a topology like this:
the separate isolated 1G physical link between esxi and switch EtherChannel just for veeam backup traffic.
on every esxi separate vmkernel port by management enabled for veeambackup traffic.
veeam backup traffic subnet is separate from production.
veeam backup server is a vm on esxi6.
my questions:
1- my vcenter server ip is in production subnet and not in veeam backup subnet and we don't want the following any traffic from any subnet to veeam backup subnet. as a result, we can now just add esxi directly in veeam backup. can we add another interface and ip for vcenter to connect to veeam backup?
2- we bound two 1G LINK in EtherChannel from each esxi host. is this really doubled bandwidth in backup? is this really achievable? during backup just one link has traffic.
-
- Novice
- Posts: 9
- Liked: never
- Joined: Nov 17, 2020 3:55 pm
- Full Name: Babak Pirouznia
- Contact:
-
- Veeam Legend
- Posts: 821
- Liked: 128 times
- Joined: May 11, 2018 8:42 am
- Contact:
Re: seperate vcenter ip for veeam
Hello,
1- If I understand it correctly, Vmware support multihomed vcenter and one of the use case is to separate backup traffic : https://docs.vmware.com/en/VMware-vSphe ... D32C3.html
2- You bound 2x1G on management port group ? Are you using network mode transport on your proxy ? Only this mode will use your management traffic and it's not recommended on 1G network because it will use only 40% of the maximal bandwith due to the vmware API limitation
All requirements for ethernchannel are mentionned here : https://kb.vmware.com/s/article/1001938
1- If I understand it correctly, Vmware support multihomed vcenter and one of the use case is to separate backup traffic : https://docs.vmware.com/en/VMware-vSphe ... D32C3.html
2- You bound 2x1G on management port group ? Are you using network mode transport on your proxy ? Only this mode will use your management traffic and it's not recommended on 1G network because it will use only 40% of the maximal bandwith due to the vmware API limitation
All requirements for ethernchannel are mentionned here : https://kb.vmware.com/s/article/1001938
-
- VP, Product Management
- Posts: 7077
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: seperate vcenter ip for veeam
In the end we depend on the DNS FQDN resolution.
The APIs within VMware always works with the FQDNs even when you register ESXi hosts by IP address to the vcenter.
If you want to change the IP address that Veeam is using with the vcenter/ESXi hosts, then you need to give Veeam the IP addresses back on the FQDN name of vcenter and esxi hosts (as added in the configuraiton of the ESXi host).
Simplest solution is to add vcenter and ESXi host entries in the local hosts file that point to the non default IP addresses of the B&R Server and all Proxy Servers.
The APIs within VMware always works with the FQDNs even when you register ESXi hosts by IP address to the vcenter.
If you want to change the IP address that Veeam is using with the vcenter/ESXi hosts, then you need to give Veeam the IP addresses back on the FQDN name of vcenter and esxi hosts (as added in the configuraiton of the ESXi host).
Simplest solution is to add vcenter and ESXi host entries in the local hosts file that point to the non default IP addresses of the B&R Server and all Proxy Servers.
Who is online
Users browsing this forum: No registered users and 46 guests