In Vsphere 7.0  a feature was released that allows administrator to tag the vmk, for NBD specific traffic when the tag vSphereBackupNFC is applied.

This offers two benefits:

1) Isolation of NBD traffic 

2) Ability to migrate on non-default esx networks when one does not have root password credentials to share to MTV.

This task requires us to: 

Compare single vm and 10 vm using vSphereBackupNFC network label with vsphere provider without giving esx credentials and just using defaults without network selection on mtv side, and see that the additional interface dedicated to NFCbackup is used in the logs. We'll want to see if there is any cost in performance that we can share or document.

Setup

Please setup an additional interface with 172.16 ip address for this FC Host.

The FC host should have 2 (172.16 IP addresses)

Goto Network settings on the host and please edit the  newly added vmk in Network settings,

apply the following enabled services:

(vsphere replication NFC)  and (vsphere Backup NFC)

Transfer 1 VM
Transfer 10 VM

Check that the log shows NFCtransfer shows the correct 172.16 interface was used.
Please then re-test 1 vm using: only  (vsphere Backup NFC)  service and  disabling/removing  service (vsphere replication NFC) from the vmk that was previously had both services enabled.  The reason for this additional check is to see if it will work correctly with only that service added.  in MTV-1200 ticket Kyle says he needed to apply both network labels however its not clear if they are both needed.

For more details see MTV-1200, or refer to screen shot: https://vnote42.net/2022/08/10/how-to-isolate-nbd-backup-traffic-in-vsphere/  

We may consider also using vlans, and networkattachments to simulate more realistic segregation of backup network if desired.