Quantcast
Channel: VMware Communities : Popular Discussions - Backup & Recovery
Viewing all articles
Browse latest Browse all 64650

VADP using NBD: what network port on ESX server is used for data transfer?

$
0
0

I've gone through a bunch of VMware documentation (including the API guide) and can't seem to find this documented anywhere.

 

I have an environment where we will be bringing 10GbE ports online on a couple of ESX servers and want to make sure the VADP traffic uses that port. This will be a dedicated flat network so I'm assuming ESX will be smart enough to resolve the proxy host (this is with NetBackup 7.1 with VMware Access Host), see what network its on and send out the traffic through the appropriate interface.

 

If you have multiple VMkernel ports defined (for example, one dedicated   for vMotion and another on a separate VLAN or dedicated 10GbE link for   NFS datastores or dedicated for mangement traffic), what is the logic  to  decide which VMkernel port to use?

 

I know with ESXi this changes slightly as there no longer a service  console port, and when configuring a new network port you only have  connection types for Virtual Machine (VM port group) or VMkernel. But  when adding a VMkernel port, you can specifically select the port  properties to include: vMotion, Fault Tolerance logging and Management  Traffic. I guess the question there is: do any of these port properties  HAVE to be selected in order for the NFC traffic to use the port, or  will it use any VMkernel port... and if so, which VMkernel port  (hopefully it will be smart enough to try to use one on the same subnet  if it exists). And if any of the properties are selected (vMotion, Fault Tolerance logging or Management Traffic), would this specifically EXCLUDE those interfaces for NBD (NFC) traffic?

 

Any help or pointers to where this is documented would be great.

 

Thanks.


Viewing all articles
Browse latest Browse all 64650

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>