SureBackup Fails When Using Static Mapping Option

[EskBackupGuy23]

Hello -

Veeam Support Case: Case #07200883 - SureBackup LAB Configuration - Static Mapping causing Destination Host Unreachable

SureBackup LAB Configuration: (Names and addresses have been changed to protect the innocent )

Lab name: LAB - Satellite - NEW
Host name: topsecret.ciaheadquarters.com

Appliance:
Name: LAB_-_Satellite_-_NEW
Folder: LAB - Satellite - NEW
Production network: vlan 172
IPv4 address: 10.17.2.51
IPv4 subnet mask: 255.255.255.0
IPv4 default gateway: 10.17.2.1
IPv4 preferred DNS server: x.x.x.x
IPv4 alternate DNS server: x.x.x.x

Network configuration type: advanced single-host

Network options:
Isolated network: LAB - Satellite - NEW vlan 172
IPv4 masquerade address: 10.255.231.0
IPv4 appliance address: 10.17.2.1
IPv4 DHCP: disabled
Isolated network: LAB - Satellite - NEW vlan 160
IPv4 masquerade address: 10.255.222.0
IPv4 appliance address: 10.16.0.1
IPv4 DHCP: disabled
Isolated network: LAB - Satellite - NEW vlan 168
IPv4 masquerade address: 10.255.220.0
IPv4 appliance address: 10.16.8.1
IPv4 DHCP: disabled

Network mapping:
vlan 172 --> LAB - Satellite - NEW vlan 172
vlan 160 --> LAB - Satellite - NEW vlan 160
vlan 168 --> LAB - Satellite - NEW vlan 168

Static mapping:
10.16.0.50 --> 10.17.2.61 (Access: Production ---> LAB)

Anytime I use the Static mapping option, my SureBackup job will fail due to ping not being able to ping the isolated and/or masqueraded IP.

When I uncheck the Static mapping option, the SureBackup job is 100% successful. It is very bizarre.

This was working for me in Veeam 11 and 11a. Once I upgraded to Veeam 12.1.1.56 is when I started having this issue.

Any ideas on this one would be greatly appreciated!

Thank you!
Ron

[david.domask]

Hi Ron,

Thank you for including the case number; from initial look at your post and case, not sure I can immediately spot the issue, and based on Engineer's notes, looks like they're trying to reproduce the same process you had (v11a setup with similar configuration, upgrade to 12.1.1.56, see if failure invokes), so looks like the focus is to try to narrow the troubleshooting here if it reproduces. I can see the case has been pretty active from both sides (much appreciated on your availability for that), so I think allow the Support Engineer additional time for their testing.

[EskBackupGuy23]

David -

Thank you. Yes, I figured I would post this issue in here in hopes that someone else has ran into it as well. Yes, I am awaiting the Veeam Engineer to try and replicate issue in his lab environment.

[EskBackupGuy23]

This has been resolved. Was picking my 10.17.x.x backup vlan thinking the Access IP would bind to that.

Instead, when I pick the corresponding network from the list that the machine is actually connected to, it binds the access ip and routes correctly.

Thanks Veeam Support!

Ron

[david.domask]

Glad to hear that you and Support were able to fix it and thank you for the follow up and the solution here.