-
- Enthusiast
- Posts: 27
- Liked: never
- Joined: Jan 10, 2017 3:06 pm
- Full Name: Chris Johnson
- Contact:
SureBackup job failing on ping test
Hi
I am struggling to get SureBackup to work as they keep failing on the ping test, my setup is as follows
We use the following VLANs
VLAN 130 (Backup)
VLAN 90 (Server VMs)
The Veeam backup servers IP is 10.10.130.5 and it sits on VLAN 130
The VM I am testing SureBackup on is 10.10.90.20 and it sits on VLAN 90
I have created the application group for the above and the virtual lab and the configuration is as follows
Destination is the same host the VM is running on.
Proxy is set to the same virtual switch as the VM uses and has a static address of 10.10.90.230.
Advanced single-host
Isolated Network, I ticked VLAN ID and set it to 90 for Production Network and left the Isolated Network as 90
Network Settings, the IP address is the same IP as the production gateway and the masquerade address are configured 10.255.254.
And no static mappings.
Firstly if I manually boot the virtual lab, I can ping the Veeam server from within the lab, I can also ping the lab on 10.10.90.230 from any machine on the network including the Veeam backup server.
If I trace route from the backup server to the virtual lab there are two hops
10.10.130.254
10.10.90.230
If I run the job the heartbeat test works fine but it fails on the ping test, the test tries to ping 10.255.254.20.
When the job is running I connected to the appliance and couldn't ping the address above, I also connected to the VM created by SureBackup and did an IPConfig and it listed the IP as 10.10.90.20, I could ping 10.10.90.254 but couldn't ping the Veeam server, is it worth trying to ping the virtual lab on 10.10.90.230?
If it helps a trace route on the VM to 10.10.90.254 is 1 hop.
No firewall is enabled on the VM being restored by SureBackup whilst I test.
I found the below information on a Veeam KB, is this likely to be my issue?
"If you assign to the proxy appliance an IP address from the same network where the backup server is located, Veeam Backup & Replication will automatically add a new route to the routing table on the backup server. If you assign to the proxy appliance an IP address from a different network, you will have to manually add a new route to the routing table on the router in the production network. If you do not add a new route, tests and application scripts will fail and you will not be able to access VMs in isolated networks.
When Veeam Backup & Replication starts a virtual lab, it verifies if the proxy appliance is available by sending a ping request to it. If the corresponding route is not added to the routing table, the SureBackup job will fail."
Anything else I can test?
I had a support case open a few weeks/months ago 02246430 and I am just revisiting the issue.
It looks to me like the masquerade isn't working?
Any help/advice appreciated.
Many thanks
I am struggling to get SureBackup to work as they keep failing on the ping test, my setup is as follows
We use the following VLANs
VLAN 130 (Backup)
VLAN 90 (Server VMs)
The Veeam backup servers IP is 10.10.130.5 and it sits on VLAN 130
The VM I am testing SureBackup on is 10.10.90.20 and it sits on VLAN 90
I have created the application group for the above and the virtual lab and the configuration is as follows
Destination is the same host the VM is running on.
Proxy is set to the same virtual switch as the VM uses and has a static address of 10.10.90.230.
Advanced single-host
Isolated Network, I ticked VLAN ID and set it to 90 for Production Network and left the Isolated Network as 90
Network Settings, the IP address is the same IP as the production gateway and the masquerade address are configured 10.255.254.
And no static mappings.
Firstly if I manually boot the virtual lab, I can ping the Veeam server from within the lab, I can also ping the lab on 10.10.90.230 from any machine on the network including the Veeam backup server.
If I trace route from the backup server to the virtual lab there are two hops
10.10.130.254
10.10.90.230
If I run the job the heartbeat test works fine but it fails on the ping test, the test tries to ping 10.255.254.20.
When the job is running I connected to the appliance and couldn't ping the address above, I also connected to the VM created by SureBackup and did an IPConfig and it listed the IP as 10.10.90.20, I could ping 10.10.90.254 but couldn't ping the Veeam server, is it worth trying to ping the virtual lab on 10.10.90.230?
If it helps a trace route on the VM to 10.10.90.254 is 1 hop.
No firewall is enabled on the VM being restored by SureBackup whilst I test.
I found the below information on a Veeam KB, is this likely to be my issue?
"If you assign to the proxy appliance an IP address from the same network where the backup server is located, Veeam Backup & Replication will automatically add a new route to the routing table on the backup server. If you assign to the proxy appliance an IP address from a different network, you will have to manually add a new route to the routing table on the router in the production network. If you do not add a new route, tests and application scripts will fail and you will not be able to access VMs in isolated networks.
When Veeam Backup & Replication starts a virtual lab, it verifies if the proxy appliance is available by sending a ping request to it. If the corresponding route is not added to the routing table, the SureBackup job will fail."
Anything else I can test?
I had a support case open a few weeks/months ago 02246430 and I am just revisiting the issue.
It looks to me like the masquerade isn't working?
Any help/advice appreciated.
Many thanks
-
- Veeam Software
- Posts: 649
- Liked: 170 times
- Joined: Dec 10, 2012 8:44 am
- Full Name: Nikita Efes
- Contact:
Re: SureBackup job failing on ping test
Yes, you are correct and this KB is applicable to your case.
Backup server have routing adjusted automatically, so it knows that packets to the 10.255.254.x should be directed to 10.10.90.230.
However since there is additional hop, packets first come to 10.10.130.254, and that device does not forward packets, since it does not have corresponding routing rule.
You need to set that up accordingly, so it will send packets to Virtual Lab appliance instead of dropping it.
Backup server have routing adjusted automatically, so it knows that packets to the 10.255.254.x should be directed to 10.10.90.230.
However since there is additional hop, packets first come to 10.10.130.254, and that device does not forward packets, since it does not have corresponding routing rule.
You need to set that up accordingly, so it will send packets to Virtual Lab appliance instead of dropping it.
-
- Enthusiast
- Posts: 27
- Liked: never
- Joined: Jan 10, 2017 3:06 pm
- Full Name: Chris Johnson
- Contact:
Re: SureBackup job failing on ping test
ok so who my route look like below
route add 10.255.254.0 mask 255.255.255.0 10.10.90.230
The masquerade IP is 10.255.254.X
The subnet is 255.255.255.0
The virtual lab is 10.10.90.230
I just tried the above command and it failed, do I need to reboot the backup server? Or is the command wrong?
After I added it the route table looks like this
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.10.130.254 10.10.130.5 261
10.10.130.0 255.255.255.0 On-link 10.10.130.5 261
10.10.130.5 255.255.255.255 On-link 10.10.130.5 261
10.10.130.255 255.255.255.255 On-link 10.10.130.5 261
10.255.254.0 255.255.255.0 10.10.90.230 10.10.130.5 6
route add 10.255.254.0 mask 255.255.255.0 10.10.90.230
The masquerade IP is 10.255.254.X
The subnet is 255.255.255.0
The virtual lab is 10.10.90.230
I just tried the above command and it failed, do I need to reboot the backup server? Or is the command wrong?
After I added it the route table looks like this
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.10.130.254 10.10.130.5 261
10.10.130.0 255.255.255.0 On-link 10.10.130.5 261
10.10.130.5 255.255.255.255 On-link 10.10.130.5 261
10.10.130.255 255.255.255.255 On-link 10.10.130.5 261
10.255.254.0 255.255.255.0 10.10.90.230 10.10.130.5 6
-
- Enthusiast
- Posts: 27
- Liked: never
- Joined: Jan 10, 2017 3:06 pm
- Full Name: Chris Johnson
- Contact:
Re: SureBackup job failing on ping test
sorry just re-read that and I need to add the route on our Cisco core so that 10.255.254.0 forwards to 10.10.90.230?
Is it recommended to only have one virtual lab and then have all SureBackups restoring jobs to one host?
Otherwise the route would have to be specific for each virtual lab? And we couldn't just use one subnet.
Is it recommended to only have one virtual lab and then have all SureBackups restoring jobs to one host?
Otherwise the route would have to be specific for each virtual lab? And we couldn't just use one subnet.
-
- Veeam Software
- Posts: 649
- Liked: 170 times
- Joined: Dec 10, 2012 8:44 am
- Full Name: Nikita Efes
- Contact:
Re: SureBackup job failing on ping test
Yes, you need either place Backup server and Virtual Lab server to the same subnet, or add routing rule to your hardware (Cisco in your case).
Since first option is not available to you, you need to use second one.
There is no strict recommendation of using one Lab versus several ones. It depends on the number of machines you want to test, number of hosts available and so on.
If you want to use several labs simultaneously, you can make different masquerades for different labs and adjust rules accordingly.
For example, Lab 10.10.90.230 use masquerade 10.255.254.x, another Lab (say 10.10.90.231) use masqerade 10.255.253.x.
Since first option is not available to you, you need to use second one.
There is no strict recommendation of using one Lab versus several ones. It depends on the number of machines you want to test, number of hosts available and so on.
If you want to use several labs simultaneously, you can make different masquerades for different labs and adjust rules accordingly.
For example, Lab 10.10.90.230 use masquerade 10.255.254.x, another Lab (say 10.10.90.231) use masqerade 10.255.253.x.
-
- Veteran
- Posts: 600
- Liked: 66 times
- Joined: Jun 13, 2013 10:08 am
- Full Name: Paul Kelly
- Contact:
Re: SureBackup job failing on ping test
I've been struggling for a VERY long time to get my head around this concept, i.e. understand exactly what needs routing to where & this topic might be getting me to the closest so far!
So, are we saying that to be able to run a vLab (proxy) on a network different than the backup server, e.g. proxy on a remote site, then the Backup server MUST be able to route to ALL masquerade networks configured in ALL proxies on remote sites? Furthermore, this routing MUST be configured at the switch/hardware level? (our networking is also Cisco - with a dedicated P2P link between the two sites)
So, are we saying that to be able to run a vLab (proxy) on a network different than the backup server, e.g. proxy on a remote site, then the Backup server MUST be able to route to ALL masquerade networks configured in ALL proxies on remote sites? Furthermore, this routing MUST be configured at the switch/hardware level? (our networking is also Cisco - with a dedicated P2P link between the two sites)
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: SureBackup job failing on ping test
Hi, Paul, yes, your understanding is correct, routing must be configured on a hardware level.
Who is online
Users browsing this forum: No registered users and 19 guests