Since management traffic is carried through VMkernel adapter, I'm really confused with what you've said. Please elaborate.In other words, it is not the kernel interface for storage that is getting used during replication, it is the management interface.
That's not necessary if the target proxy utilizes hot-add mode. In this case all disk data will flow via the network which the proxy VMs belong to.Moral of the story seems to be make sure that the ESXi host (or vCenter) that is the target for replication has a 10Gbe interface for management
Would you confirm that it was indeed Direct SAN mode on the source side please? To do that you need to check the job session and see if there is "[san]" string in there. The management interface being utilized up to 50% during Direct SAN mode does not seems right.I also ran a backup which should use SAN mode on the source and target side. I surprised to see the 1Gbe interface for the management network in production (source) was quite active during backup with utilization according to SFlow sitting at 50%.
Using guest interaction proxy vProxy2 (Same subnet)
Inventorying guest system 0:00:02
Preparing guest for hot backup 0:00:04
Creating VM snapshot
Getting list of guest file system local users
Collecting disk files location data 0:00:12
Removing VM snapshot 0:00:02
Queued for processing at 12/4/2017 12:26:00 AM
Required backup infrastructure resources have been assigned 0:04:50
VM processing started at 12/4/2017 12:30:55 AM
VM size: 60.0 GB (19.9 GB used)
Saving [VMWare3] Licensing/Licensing.vmx
Saving [VMWare3] Licensing/Licensing.vmxf
Saving [VMWare3] Licensing/Licensing.nvram
Using backup proxy vProxy1 for retrieving Hard disk 1 data from storage snapshot
Hard disk 1 (60.0 GB) 1.1 GB read at 322 MB/s [CBT]0:00:21
Truncating transaction logs 0:00:01
Busy: Source 99% > Proxy 26% > Network 57% > Target 0%
Primary bottleneck: Source
Network traffic verification detected no corrupted blocks
Processing finished at 12/4/2017 12:32:10 AM
Since it is NBD mode, the proxy connects to ESXi hosts on VMkernel interfaces by DNS name resolution and use this connection to transport data. If you want to change that behaviour you need to use Virtual appliance/Hot-add mode on the target proxy.The question becomes which interface the data coming into on the host?
The injection is small and should not cause spikes. Another question - does your vProxy reside on the same network with the VMs in the job?y guess is vProxy2 which is my guest interaction proxy is utilizing the 1Gbe management network during backup to do its injection.
That's correct.Is that correct?
It does not make any difference for backup as long as the required infrastructure is accessible by the corresponding backup components.My core switch/router routes at wire speed so would it make any difference if I have several different vlans involved?
As far as I understand, neither Proxy1 nor Proxy2 has an access to ESXi management network, and that makes me wonder which proxy is being used. Which server has an access to ESXi management network?No available proxies are running on ESX(i) management interface subnet. Using proxies from a different subnet, performance may be impacted.
Users browsing this forum: Google [Bot] and 41 guests