Recovery Plan Data Lab

[FlatWhite]

Hi all,

Testing a Veeam Recovery Orchestrator (RO) plan using the Restore from Backup → Testing with DataLab\Quick test\1hour option, and the plan fails during the OS boot verification step with:Skipping OS boot-up verification because VM has no network adapters, failed to get IP address.
The same VM works perfectly in a SureBackup job using the same DataLab. What do we need to check ?

[Alec King]

Hello!
In this situation the issue is almost always network mapping conflicts. Does the VM actually get connected to a virtual network when VRO runs the test?

When executing a VRO datalab test, we have to reconcile TWO sets of network mappings -
- mappings configured in the VRO recovery location for this plan
- mappings configured in the vritual lab (on VBR) that VRO will use

And VRO does attempt to perform "implicit" mappings, meaning that even if a source network is not specified we will try to figure out which network is implied (e.g. VRO recovery location maps network A to network B for production recovery; and the virtual lab in VBR maps network B into isolated-network-B; then VRO will automatically map VMs on network A into isolated-network-B for the test)

This is complex logic and things can go wrong!
You can post here the relevant network mappings (from VRO and from VBR) and we can try to analyse that - although it would probably be quicker to take a log export from VRO and then raise a support case.

[FlatWhite]

Hi Alec,

Thanks for the response. Case has been raised #02995645, logs attached for analysis.