Hi folks, a customer using Hyper-V has this configuration on their vSwitches:
- VM servers on different VLANs/Subnets
- A vSwitch for the host, with uplinks to the physical switches that evidently connect to trunk ports
- VLAN tags are applied on Hyper-V
see: -> https://drive.google.com/file/d/1N7SMef ... sp=sharing
I’m running into difficulties because the VirtualLab appliance can only have one vNIC on the isolated Lab vSwitch, so… I could group the VMs on the various VLANs into separate Application Groups, each with its own dedicated appliance and a separate SureBackup job.
But, as you can imagine, if I need to run a SureBackup of an “WebSite” Application Group on 10.1.10.x, and it needs DNS/DC services from 10.1.1.x to function and be properly tested, that’s a problem—because even if I power on all the relevant VMs on the same isolated vSwitch, they won’t be able to communicate with each other.
I don’t know if this Hyper-V configuration is recommended, but it seems unfriendly to Veeam/SureBackup. Have you ever encountered this situation? Is there something I'm missing, a workaround or something to avoid redefining Hyper-V networking on production?
- VM servers on different VLANs/Subnets
- A vSwitch for the host, with uplinks to the physical switches that evidently connect to trunk ports
- VLAN tags are applied on Hyper-V
see: -> https://drive.google.com/file/d/1N7SMef ... sp=sharing
I’m running into difficulties because the VirtualLab appliance can only have one vNIC on the isolated Lab vSwitch, so… I could group the VMs on the various VLANs into separate Application Groups, each with its own dedicated appliance and a separate SureBackup job.
But, as you can imagine, if I need to run a SureBackup of an “WebSite” Application Group on 10.1.10.x, and it needs DNS/DC services from 10.1.1.x to function and be properly tested, that’s a problem—because even if I power on all the relevant VMs on the same isolated vSwitch, they won’t be able to communicate with each other.
I don’t know if this Hyper-V configuration is recommended, but it seems unfriendly to Veeam/SureBackup. Have you ever encountered this situation? Is there something I'm missing, a workaround or something to avoid redefining Hyper-V networking on production?
Statistics: Posted by tinto1970 — Mar 25, 2025 5:02 pm