Restore server agent backup to Hyper-v

[Tutek]

Hi,
Is any other way to restore agent windows server backup other than instant vm recovery? I would restore my windows server backup to hyper-v host but when I do instant recovery when I open console to restored VM I have no network connectivity, network card was mapped during restore and is visible in VM, network cable is attached on hyper-v host everything is checked, but on restored VM I have no connectivity, I cannot even PING network gateway. Maybe I should do first "Migrate to Production" to have network running?

[HannesK]

Hello,
you could also do export to VHDX and create the VM manually https://helpcenter.veeam.com/docs/backu ... ml?ver=110

Instant recovery must work without "migrate to production". If not, then something is misconfigured. support should be able to help what went wrong.

Best regards,
Hannes

[Dima P.]

Wojciech,

Please check defender/firewall configuration and make sure the network adapter is properly reconfigured on instantly recovered VM. Thanks!

[Tutek]

Network adapter profile on restored VM was assigned as Public, but I completely disabled firewall on all network profiles, this is very strange behawior, as I said I cannot ping netwok card gateway, from hyper-v host I can ping gateway (the same network).
Now I'm trying to do export VHDX from backup and create manually VM.

[Tutek]

After exported vhdx file and manualny creation of the VM, everything is working, all network connections are working. So there is any problem with live restore.

[Dima P.]

Wojciech,

Thanks for the update, glad you nailed it. I'll ask QA team to check this behavior and note a bug if we can confirm it in our lab!

[ChristineAlexa]

I can verify how to reproduce it on my setup
- Network Adapter is managed by a Network Controller
- Network Adapter has a Classification assigned to it.


The Classification for the adapter isn't always set during the restore/reattachment to SCVMM. This causes the networking filtering (it appears) to not allow network connectivity because of this classification mismatch.

Setting the Classification back to whatever it was set to before the restore has solved it on every machine I've had that on.

In some cases, the VM Network is lost as well

So both scenarios can cause the VM not to have proper network connectivity

Hope that helps track down how to resolve it (Had this bug bite me on 3 restores lately)

HTH
Christine

[Dima P.]

Hello Christine,

Thanks for the detailed update, passed this info to RnD folks for a review!

[Dima P.]

Christine,

These settings are controlled outside guest operating system where agent is installed, so basically agent knowns nothing about the hypervisor network configuration thus does not collect and restore these settings. Thanks!