why backup proxy not work correctly during backup job ?

[baber]

Dear all
Hi

i have a question about backup proxy:

i know if i want send backup traffic from other vmnic have to create a backup proxy
my veeam ip adress is 10.11.21.199 and i have installed a new server with ip address 10.11.21.197 (proxy server)
add proxy server(10.11.21.197) to my repository proxy
now when i create a new backup job in backup proxy select 10.11.21.197
veeam server is connected to vmnic1
and backup proxy is connected to vmnic2
now actuarly when i start backup job all of backup traffic had to send from vmnic2 but it send from vmnnic1
why backup proxy not work correctly?

BR

[nielsengelen]

So you have 2 servers installed? I am confused about the VMNIC1 and VMNIC2 part. Could you explain what behaviour you see during the job or what the log says?

[baber]

dear friend
Hi

i have 3 server on my esxi host

vcsa = 10.11.21.192 on vmnic1
veeam = 10.11.21.199 on vmnic1
backup proxy = 10.11.21.197 on vmnic2

i monitor network usage on my esxi host when in job i select backup proxy (10.11.21.197) all of backup traffic have to send from vmnic2 but most of traffic sent from wmnic1

why ?

[nielsengelen]

Are they connect to the same vSwitch? This looks more of a VMware issue / question then Veeam if it goes outside the machines.

[baber]

no they are connect to different switches

veeam is on dvs switch and backup proxy is on vss switch

[tdewin]

By any chance, do you still have the default proxy enabled. It could be that in this case, the default proxy on the backup server was selected to be the proxy

[baber]

By any chance, do you still have the default proxy enabled. It could be that in this case, the default proxy on the backup server was selected to be the proxy

now i disable default proxy and another run jub but send most of trraffic from default proxy

why ??

[nielsengelen]

I would advise to contact support for insight as it is hard to understand without this.

[aich365]

Are these all Virtual Machines running proxy?
If one is a physical machine it will not use hot-add and jobs will queue on the other proxies rather than run nbd on a physical server.

[baber]

so thanks

but i don't have any physical server all of them are vms and the other hand i disable all of my proxy server on veeam and just enable one proxy on veeam

[foggy]

Any chance the repository is CIFS share presented to the backup server?

[baber]

my new backup proxy is a path on windows server

[foggy]

The it's better to ask support for assistance.

[Henrik.Grevelund]

Hi Baber

To figure out which traffic you are seeing you need to understand the routes of data(not knowing your knowlegde):
ESXi kernel port -> (Backup data path) -> backup proxy
Backup proxy -> (Compressed backup data path) -> Backup repository
Backup proxy -> (Control data) -> VBR server
Backup repository -> (Control data) -> VBR server

If the backup proxy is virtual machine and the datastore of the virtual machine in the backup is available to the backup proxy's ESX host, it will use Hotadd(transport mode: virtual appliance). This will eliminate the "Backup data path" part.
You have 3 ESXi host, and the proxy is running on 1 of them. So maybee the hotadd isnt possible for virtual machines running on the 2 other.

Not sure if it helps ?

Have a nice weekend,
Henrik

[baber]

if my backup proxy is on vm do i have to choose virtual appliance for transport mode??

[foggy]

It will be selected automatically in case it is available and automatic transport mode selection is enabled.