SureBackup issues duplicate IPs

[AlexHeylin]

Case #07151125

SureBackup can create duplicate IPs which causes ping and check scripts to fail. One source VM involved set to static IP, this may be related.
You'll see a message in the SB task log about isolated NIC with a 169.* auto-assigned address.

This one smells like a bug.

[Mildur]

Hi Alex

Our support team will escalate it to RnD if it get's confirmed as a bug.
Please continue to work with them. You can always request an escalation through our Talk to Manager option if required.

Best,
Fabian

[AlexHeylin]

Not exactly a bug - but unexpected behaviour (likely by Hyper-V) and the docs show doing something that can cause this issue to become evident.

It seems that under some unidentified circumstances Hyper-V can treat VLAN n on a private vSwitch as being the same network as VLAN n on an External (production) vSwitch. As the docs https://helpcenter.veeam.com/docs/backu ... with-vlans currently show using the same VLAN ID for production and isolated networks (vSwitches) this can cause the SB VMs to come online connected to the production network - even though they're connected to a Private vSwitch and should not be able to talk to anything outside of that switch (except via the vLab proxy etc).

This causes IP conflicts for machines with static IPs - like AD DCs. Docs are going to be updated to show and state need to use different unique VLAN IDs, and that the isolated VLAN(s) should not use VLAN IDs used in production (which is what's currently shown).