Skip to main content
Question

SureBackup and Hyper-V with multiple VLANs/Subnets

  • January 12, 2026
  • 1 comment
  • 6 views

Hello! I am attempting to set up SureBackup to test backups of VMs from my Hyper-V environment in a way that mimics production and simulates interactions of VMs in separate, routed subnets, but I am running into issues setting up the isolated network’s NICs on the proxy appliance. It is unclear if I’m misunderstanding the setup documentation or if I am running into a limitation caused by the logical network of my Hyper-V cluster.

My Hyper-V hosts have a single logical switch for VM traffic with all VLANs trunked to it from the physical switch that the hosts are connected to. Each VLAN has a unique subnet of varying size, mostly /24 but there are some /23 and /27 networks.

I am trying to create a Virtual Lab in advanced single-host mode with an isolated network for each subnet containing a VM being tested, with the proxy appliance acting as the router for each subnet.

The two subnets I am testing with are:

  • 192.168.124.0/23 (VLAN 124)
  • 192.168.196.32/27 (VLAN 209)

I am mapping these VLANs to VLAN 395 and 396 respectively when creating the isolated networks. This seems to work fine.

When setting up the vNICs for the proxy appliance, I set the first vNIC as follows:

  • vNIC 1
    • IP address: 192.168.124.1 (the default gateway the production VLAN 124)
    • Mask: 255.255.254.0 (/23)
    • Masquerade address: 172.16.124.D (matching the third octet of production for simplicity)

I originally tried to set up the second vNIC for VLAN 209’s corresponding isolated network as:

  • vNIC 2
    • IP address: 192.168.196.33 (VLAN 209’s default gateway in production)
    • Mask: 255.255.255.224
    • Masquerade address: 172.16.196.33

and the vNIC Connection Settings window told me the second vNIC couldn’t be added because the network did not match the masquerade network address. I assumed this was because the two vNICs masquerade addresses need to be in the same network. When I change the mask of vNIC 2 to match the first vNIC, the last octet of the masquerade address becomes ‘D’ like the first vNIC and is no longer editable. When trying to add the vNIC with this configuration, I get “vNIC with such isolated network connected already exists.” It seems odd to me that you cannot have separate subnets for the masquerade addresses that correspond to the ‘real’ subnets in the isolated network.

Am I misunderstanding how the isolated networks and their masquerade addresses are supposed to be architected?

1 comment

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • January 12, 2026

IIRC the masquerade network allows only one IP address so you cannot have two.  I am checking the docs over and doing some searches.