Microsoft Hyper-V • Re: Best Practice and How To separate backup traffic from Production Network

Hi and thanks for the replies, much appreciated.
I had already applied the Preferred Networks option in Veeam Console and it didn't work but I think I have a root cause. Hardware level the NIC is not fully SET and SRIOV compatible. CLI was configuring it but it wasn't working properly and CLI was not generating error messages. Ignore anyone that says NDIS 6.5 support drivers are sufficient for SET is probably the best answer. Low level the NIC must support certain hardware features too.

Going forward I have specified a certified Intel NIC for the new server and hopefully will deploy the following across a pair of 4 port NIC.
4 x NIC ports (two from each physical NIC) in SET for VM traffic
2 x NIC ports (one from each physical NIC) in SET for Backup
2 x NIC ports (one from each physical NIC) in either SET or LBFO/LACP if that is possible as it will remove the Management NIC from the Virtual Switch layer.

Any advice on the proposed layout would be very welcome.
Thanks
Nick

Statistics: Posted by NickKulkarni — Oct 20, 2025 10:19 am

---