#1 Global Leader in Data Resilience

"No destination network for IP address" error during SureBackup

KB ID: 4070
Product: Veeam Backup & Replication
Published: 2020-12-01
Last Modified: 2023-01-31
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

A Surebackup job fails with the error "Error: No destination network for IP address"

Selecting the individual server from the list of VMs within the status window the following is seen:

Cause

When a VM is Powered On by the SureBackup job, Veeam Backup & Replication will detect its IP address. If the detected IP address does not match the Virtual Lab's isolated vNIC subnet, the error "No destination network for IP address" will occur.

Solution

Training Video

We encourage you to watch this 15 minute video which covers how the Virtual Lab works, and how to configure it.

https://www.veeam.com/videos/virtual-lab-configuration-15466.html

If this error occured while using "Basic single-host" on the Networking tab, switch to "Advanced single-host" and manually configure the correct Isolated Networks, and appropriate  Network Settings for those Isolated Networks. For more information on configuring SureBackup with "Advanced single-host" please watch the video above, or review the following documentation:
https://helpcenter.veeam.com/docs/backup/vsphere/create_vlab.html

 


 

To resolve this issue review the Network Settings of the Isolated Networks within the Virtual Lab. The IP address in the Network Settings must match the gateway IP that the VM being powered on by the SureBackup job is expecting.

If the IP in Network Settings is correct, make sure that the Mask also matches production as this could cause the wrong subnet to be specified.

 



Example:

For the error show at the begining of this KB article, the settings which caused this to happen were as shown here:

After reviewing the network settings of the production server, the issue was identified. As shown in the screenshot below the gateway IP that the server is expecting does not match the VLab's Network Settings above. The combination of the incorrect IP address with the correct Mask has caused the Virtual Lab to be expecting the VM to have an IP in the 192.168.148.1/24 subnet. Which is exactly why when the VM presents with the IP 192.168.0.3 the error "No destination network for IP address" occurs.

The Network Settings were corrected as shown below, and the SureBackup job worked.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.