Feature Request - Re-IP support for subnets smaller than /24

[ToddD]

We are using Veeam to replicate VMs to our DR site, some of these VMs us subnets divided up with a 255.255.255.240 or /28. When I was building the re-IP rules, I noticed you cannot specify the gateway IP on the source VM, without this option, Veeam cannot differentiate between VMs using IP address from subnets smaller than 255.255.255.0 or /24 when using the wildcard variable in the last octet. I checked with Veeam support with case 06084455 and confirmed this is not possible. Here is more clarification if it is needed

Example has two VMs using 10.1.36.0/28 subnetting
VM-Network-1

• Usable Range: 10.1.36.65 - 10.1.36.78

• Gateway: 10.1.36.65

VM-Network-2

• Usable Range: 10.1.36.81 - 10.1.36.94

• Gateway: 10.1.36.61

VM1 Network Configuration

• VM Network: VM-Network-1

• IP: 10.0.36.75

• Subnet: 255.255.255.240

• Gateway: 10.1.36.65

VM2 Network Configuration

• VM Network: VM-Network-2

• IP: 10.0.36.90

• Subnet: 255.255.255.240

• Gateway: 10.1.36.81

Inside the Veeam replication job, if I use the wildcard to match VM1
Source VM

• IP Address: 10.0.36.*

• Subnet mask: 255.255.255.240

Target VM

• IP Address: 10.1.36.*

• Subnet mask: 255.255.255.240

• Default gateway: 10.1.36.65

This rule will also match VM2 because it is only looking at the IP and subnet mask of the VM. When the rules run, Veeam will place VM2 in the correct VM network using the network mapping but assign the wrong gateway IP address. It seems if we added the option to also check the source VM by gateway, then Veeam could understand subnets smaller than a 255.255.255.0 (/24).

Thanks for your consideration

[HannesK]

Hello,
while the idea itself is valid / makes sense, it looks like only very few customers seem to miss that feature.

So I ask myself, how many VMs do you replicate that you like to re-IP? If it's only a few, then you could add a few 1:1 rules. Alternatively, create many 1:1 rules with PowerShell.

Best regards,
Hannes

[ToddD]

We replicate around 200 VMs but only run into this issue on around 10 VMs today that are segmented with /28 networks, to your point I could create 1:1 rules. The only reason I'm against the 1:1 rules is now this is something that needs to be remembered by a human Personally, I feel it opens up the risk during a failover that the server would fail in the process or be off network because someone forgot to update the 1:1 rules for the VM (maybe the source was changed or migrated to a new VM). I thought the idea for the IP mappings was to help eliminate manual work in both the Veeam configuration and failover. I worry this issue will just continue to get worse as we continue to segment our network which is being driven from our security team. We do test our DR configuration to look for issues like this, but that is a reactive approach to find Veeam configuration errors so we can correct them. I'm surprised that only a few customers segment their networks smaller than /24 network. In the end, what I was hoping to have as much automation setup in my replication jobs. We use VMware tag assignment to place the VM in the correct replication job, then I wanted to have the network mapping/reIP configured to automatically handle the changes need to bring that VM up in our DR location. But if I have to manually configure the 1:1 reIP rules, it starts to take the clean automation away and require manual steps and quarterly auditing. I understand if there isn't enough customer request to justify the request, but I find it a bit odd to have a wildcard reIP feature that only works in certain circumstances. Thank you for your response, let me know if you want any more information.