Forum Discussion
Hyper-V Converged Networking for VEEAM Backups
Your diagram shows host management on VLAN 100 and the repository on untagged VLAN 200 access ports. Domain membership is not required for basic IP connectivity, but those VLANs need routing and firewall rules before the hosts can reach the repository. If the Aruba ports remain access/untagged ports, do not also tag VLAN 100 or 200 inside Windows. If you want management and backup traffic over the same SET uplinks, configure the host switch ports as trunks, create a separate ManagementOS vNIC, assign its access VLAN with Set-VMNetworkAdapterVlan, and give it an address in the backup subnet. Keep the management vNIC on VLAN 100, verify allowed VLANs and MTU end to end, then test IP connectivity and required ports before configuring Veeam. Validate SET member compatibility and bandwidth/QoS. The Veeam port requirements should come from its vendor documentation; Microsoft’s Hyper-V commands alone cannot confirm that layer.
Hi Jamony, thanks for the reply and configuration details.
The Aruba 2930M is operating as a Layer 2/3 core switch with IP routing enabled, so inter-VLAN traffic between the data and backup subnets is handled at the ASIC layer.
VEEAM does not provide specific guidance on Hypervisor converged vSwitch QoS weights.
So by the looks of things, the simplest option is to use VEEAM Backup and Replication bandwidth management using global network traffic rules which restrict source/destination subnet ranges with scheduled throttling (e.g. I can 'cap' backup jobs to 20Mbps during peak hours while keeping restore traffic unthrottled).
