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:
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.
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.