I’m having an issue with one of my SureBackup jobs. I can’t seem to get Surebackup to use the correct NIC when checking the integrity of a replication job. This job used to work, however I had to install Hamachi on the server for outside access. After installing Hamachi (which installs a virtual adapter and gives itself an IP) the SureBackup job has constantly failed with the error of “No destination network for IP address 25.x.x.x.”. Just so happens the actual IP of this server is 192.x.x.x and the Hamachi IP is 25.x.x.x. . I have this server backing-up to a few different locations as a regular backup job. SureBackup works great when checking the consistency of those backups.
I’ve tried a few fixes but to no avail. The fixes include uninstalling then reinstalling VM tools and I’ve followed the steps in KB1067 (https://www.veeam.com/kb1067). I’ve contacted Veeam Support and I was told maybe a script to disable the Hamachi NIC might be the best option. Any help would greatly appreciated.
I'll post the SureBackup Session logs for the server in question. If needed I will post the Surebackup log as well. Don't want to post it first thing due to its size.
10/12/2015 7:54:56 AM Publishing
10/12/2015 7:54:43 AM Replica point: created at 10/11/2015 12:12:40 PM, type snapshot
10/12/2015 7:54:56 AM Replica: JCAFS_replica (Status SureBackup, original location R720-ESXi1, target location R420-ESXi2)
10/12/2015 7:54:56 AM Virtual lab: Virtual Lab 1
10/12/2015 7:54:56 AM VM: JCAFS (verification, 4096 MB vRAM)
10/12/2015 7:54:56 AM OS: Microsoft Windows Server 2012 (64-bit)
10/12/2015 7:54:56 AM Network adapter 1: MAC 00:0C:29:0B:B3:3B, type generated, network VM Network
10/12/2015 7:54:56 AM Assigned roles: none
10/12/2015 7:54:56 AM Maximum boot time: 600 second(s)
10/12/2015 7:54:56 AM Application initialization: 120 sec
10/12/2015 7:54:56 AM Heartbeat test: enabled
10/12/2015 7:54:56 AM Ping test: enabled
10/12/2015 7:54:56 AM Script tests: disabled, 0 tests
10/12/2015 7:55:05 AM Reconfiguring
10/12/2015 7:55:05 AM Network 1: production VM Network, isolated Virtual Lab 1 VM Network, mapped
10/12/2015 7:55:05 AM Results: 1/1 network(s) mapped, 0 unmapped
10/12/2015 7:55:05 AM Summary: 100% total pass rate
10/12/2015 7:58:01 AM Error Powering on
10/12/2015 7:55:17 AM Waiting for OS to boot for up to 600 seconds (stable IP algorithm)...
10/12/2015 7:55:17 AM Note: Will proceed to the next step at 10/12/2015 8:05:17 AM or earlier
10/12/2015 7:58:01 AM Results: IP address 25.154.43.100 is detected
10/12/2015 7:58:10 AM Updating virtual lab parameters
10/12/2015 7:58:01 AM Error Results: no destination network for IP address 25.154.43.100
10/12/2015 7:58:01 AM Error: No destination network for IP address 25.154.43.100
10/12/2015 7:58:05 AM Powering off
10/12/2015 7:58:10 AM Unpublishing
Could you please go to "Control Panel --> Network and Internet --> Network Connections --> Advanced tab --> Advanced Settings --> Adapters and Bindings" in your guest OS where Hamachi is installed and change connections order, placing hamachi virtual adapter at the very bottom of the list, update the backup file you're running SB job from and try SB job again. Please let us know if that helps.
PTide, I disabled the Hamachi NIC, ran the replication job and then ran the surebackup job. Still getting the same error.For some reason its still trying to use the 25.x.x.x IP. Any more suggestion are gladly accepted and thank you for your help.
Does your VM have another IP besides the 25.*.*.* one? If yes, then does it even appear in job log? Also please check what does route print command show - the IPv4 Route Table is of interest.
Then please try to disable LogMeInHamachi Tunneling Engine and LMIGuardianSvc services. After that disble hamachi NIC if any present. Run replica sync again, then run SureBackup. If that won't help then please keep working with support team on that issue. As I can see from your case support has not managed to resolve the issue, so you might want to escalate the case in order to push it to a higher tier. To do that please use "Talk to manager" button.
PTide, I've tried your suggestion but I'm still seeing the same issue. I'll try to get this case pushed to a higher tier. Thank you again for you help!
