Different restore results with VRO

Hi Chris, what are the errors you’re getting?

Hi Paul,

mostly it’s “Failed to find any network connections for the VM” and “Failed to get IP address”. The VM use DHCP but the DHCP server was restored, too. And even the DHCP server and affected VM are in different VLANs the virtual lab is configured to route the traffic.

EDIT: Sometimes the restored VM didn’t have an vNIC configured

​@Madi.Cristil ​@safiya - maybe we move this to the VRO Heros Den for better help.

Hi everyone!

I did a manual restore of the VM which has no vNIC after restoring with VRO. When restoring the VM manual using full VM restore, the NIC is configured on the VM. This is weird.

Is it possible that during some runs, the timeouts are reached before the VM is ready? If you compare a successful and failed run, do you see any tasks taking more time than usual?

Does this only occur on your Linux VMs or do you have the same issue with your Windows Workloads? Depending on your Linux Distribution and/or VM-configuration, it could be, that the restored VM has no information about it’s “new” NIC / eth Interface...

just found the Thread in the R&D regarding my mention:

SureBackup networking with Linux VMs - R&D Forums

For a conclusion I have to issues: Linux VMs that don’t have any network connection. Some VMs were stated in VRO that VMware tools not running even they are installed, up and running in the restored VM. Reconfiguring the timeout doesn’t change the behaviour.

We had the reconfigured a production VM with a static MAC address because I found a thread in the forums that NICs - especially on Linux guests - bind to the MAC address. Unfortunately, this results in a restored VM without any virtual NICs.

Thanks for your help so far!

I’d like to leave a feedback how I solve the challenges partially. Configuring the VMs with a static IP instead of using DHCP solved the most of the issues. The other ones are based on VMware Tools that were not update or unsupported.