W2012 R2 Strange issue with nic teaming after restauration

[Benoit Loiseau]

Hi,

I'm testing Veeam Endpoint Backup in my lab and i'm experiencing very strange issues after bare metal recovery.

My setup is the following :

My test server under W2012R2 with veeam endpoint backup 1.5.0.306 has on single disque and 2 nic in a windows team.
I perform my backups to another server which has my instance of Veeam B&R (9.0.0.1491) and uses its local disks as backup repository.

No issue with any backup i performed everything went well.
But every time i restore with my usb recovery drive in bare metal mode, my nic team disappear and my network configuration is broken.

I need to reconfigure a single network card in order to get back my network interface working. Since recovery each time i try to get a new team configured it works until i reboot my test machine a get deleted all over again.

Anyone has ever experienced such behavior ?

[Dima P.]

Hi Benoit,

Please open a support case and post the case Id to this thread - need to check you application and reocvery logs. Thanks.

[Benoit Loiseau]

As requested : Case # 01855540

[Dima P.]

Thanks. Shared with QA team.

[Dima P.]

Update: we set up the lab with NIC teaming and run a Bare Metal Recovery and all worked, as it should. Kindly, upload the restore logs as support requested (should be automatically saved to your backup repository after bare metal restore was performed), so we could continue the investigation.

[Benoit Loiseau]

Glad to read that, waiting for the analyse of the last logs i provided in order to be sure.

[Tibo]

We have exactly the same issue here with 2012 R2 Nic teaming after a bare metal restore using Veeam Agent 2.0 and Veeam B&R 9.5 U2 as repository.

[Dima P.]

Tibo,

Please open a support case and share the case ID. Thanks!

[pfelder]

We had the same problem with a damage NIC teaming configuration after a bare metal restore on a Windows Server 2012 R2.

The problem is the driver injection during the restore. To avoid the problem, we used the following steps to recover the system:

- Boot system with Veeam Recovery Media
- go to Tools -> Load Driver
- Deactivate Option Inject these drivers into operating system while performing bare metal recovery
- go back to main menu
- Start Bare Metal Recovery

Hope this helps!

[caelum]

I can confirm this is still an issue in Veeam Agent for Microsoft Windows 3.0.2.1170 using broadcom NICs. I will be using pfelder's suggestion in the future. Thanks!

[JeWe]

Hi,

can confirm that this issue still persists in VBR 10.0.1.4854 / Agent 4.0.1.2169. Thanks for the solution @pfelder !