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
VM-Network-2
- Usable Range: 10.1.36.81 - 10.1.36.94
VM1 Network Configuration
VM2 Network Configuration
Inside the Veeam replication job, if I use the wildcard to match VM1
Source VM
- Subnet mask: 255.255.255.240
Target VM
- 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