Before I log a ticket I'm wondering if what I'm trying is even supported.
We have multiple sites with different IP ranges but the VLAN structure and network names in VMWare are consistent. For example VLAN 6 on all sites is the staff VLAN but each sites staff VLAN has it's own IP range. Nothing out of the ordinary so far.
Our CORE and DR sites both have a "Server" vlan and thats the VMWare network name on both sites but obviously they are different subnets.
My problem is that I'm trying to setup SureBackup to do some simple tests on the DC's on both sites but I can't add a vNIC for the DR site as Veeam complains there is already a vNIC for that production network (because the network names match I'm assuming) even though it's in a different site and runs a different IP range. If I try and change the name of the network in Veeam when adding the production network it lets me do that but then when running the SureBackup job it connects the VM's to the network from the other site, and since the address schemes don't match they can't route anywhere.
As far as I can tell my only option is to rename all our VMWare networks to include the site name and then change all the VM's connected to those networks. I've only just started looking at SureBackup seriously so I could be missing something here, if so can someone point me in the right direction?