Messages in SureBackup log:
[timestamp] <01> Error PowerOn failed, vmRef 'vm-xxx', hostRef 'host-x' bei Veeam.Backup.SureBackup.CSbJobPerformer.StartAppGroupTasks(CSbTaskSession taskSessions, List`1 runningTasks, CSbTaskPerformer taskPerformer)
[timestamp] <01> Error bei Veeam.Backup.SureBackup.CSbJobPerformer.ExecuteJob()
[timestamp] <01> Error bei Veeam.Backup.SureBackup.CSbJobPerformer.Execute()
[timestamp] <01> Error Module DevicePowerOn power on failed.\n bei Veeam.Backup.ViSoap.CSoapTask.WaitForTaskComplete(Int32 millisecondsInterval)
[timestamp] <01> Error bei Veeam.Backup.ViSoap.CSoapConnection.PowerOn(String vmRef, String hostRef)
Veeam B&R creates the new adaptor (with settings specified in Virtual Lab properties), however it also forces the old MAC address to be used (as you see in the vmx file of a restored machine), that's why VM fails to power on (as it's expecting to see mac address from VMware range). When the VM is started in the isolated network, Veeam tries to preserve MAC address of the VM by modifying .vmx file of the restored VM and setting up MAC from original machine. If this setting is out of standard VMware range (00:50:56:XX:XX:XX), customer may face this issue. But we can force Veeam B&R to skip preservation of an original MAC Address.
The following should fix that particular error:
1) Open registry editor
2) Go to “HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication” registry key.
3) Create a new registry key with name “SureBackup”.
4) Create a new DWORD value inside the newly created SureBackup registry key:
a. Value name is “PreserveMac”.
b. Value data is “0”.
5) Close the registry editor and restart “Veeam Backup Service” service or reboot entire Veeam Backup server.