BMR on windows 2008 R2

I am getting error when i try to boot from the BMR image from the VM client Destination, I have configured and added all the support drives for

vmx-09 drivers on Netbackup master server, still the issue exists

Backup server : Windows 2008 R2, 7.5.0.5 Netbackup Master

Error : no network interfaces were discovered

Destination Server MDS6896 : Virtual server :

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
   Physical Address. . . . . . . . . : 00-50-56-9F-13-E5
      IPv4 Address. . . . . . . . . . . : 10.220.23.20(Preferred)

Source : Windows 2008 R2

Ethernet adapter Prod Team:

mts6645

   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Prod:HP Network Team #1
   Physical Address. . . . . . . . . : B4-99-BA-5D-92-30
   IPv4 Address. . . . . . . . . . . : 10.220.19.205(Preferred)
   NetBIOS over Tcpip. . . . . . . . : Enabled

Harsha_Kumar
12 years ago
Thanks every one for help, Issue is resolved.

We have problem with the VMXNET3 adapter drivers,

we have to select the E1000 drives for the VM, since the Vmxnet3 does not support to discover the network, updated the drivers E1000 instead of vnet3.

There are couple of ways to update the drivers in ESX server

we can download the drivers and update in driver package or select the drivers in ESX server as E1000 instead of vmxnet3 drivers for network adapters.

Here is the KB from the VMWare website to update in ESX server.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003020

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805

Here is the link from the Symantec Team.

http://www.symantec.com/business/support/index?page=content&id=TECH181674

http://www.symantec.com/connect/forums/bmr-restore-no-network-interface-were-discovered

5 Replies

inn_kam
Level 6
12 years ago
NetBackup-BMR 701 release: Windows 2008 client Physical machine to virtual machine restore (Part1)

https://www-secure.symantec.com/connect/videos/netbackup-bmr-701-release-windows-2008-client-physical-machine-virtual-machine-restore-part1

Windows Device Driver Requirements for Bare Metal Restore (BMR)

Article:TECH181674 | Created: 2012-02-17 | Updated: 2012-02-17 | Article URL http://www.symantec.com/docs/TECH181674

Bare Metal Restore best practices and recommendation?

https://www-secure.symantec.com/connect/forums/bare-metal-restore-best-practices-and-recommendation
inn_kam
Level 6
12 years ago
BMR implementation

https://www-secure.symantec.com/connect/downloads/bmr-implementation
katlamudi
Level 4
12 years ago
If your VM has E1000 network adapter, then you dont need to add any special drivers. BMR default SRT is sufficient to start restore.
If you want to use VMXNET3 network adapter,
1. You need to make sure that you have added "vmxnet3 Ethernet Adapter" drivers are present on master server.

2. You have to select them to be added to "BMR Configuration" that will be used for Restore, by adding them to "Driver Packages to be used during restore" section under "Devices and Drivers"

3. What type of Shared Resource Tree(SRT) are you using? Is it Media ISO based or Networked based?
If you are using media ISO based, before creating ISO, check whether SRT has the VMXNET3 drivers or not. This can be checked as follows:
After performing Prepare To Restore, On Bootserver select "Boot Server Assistant" tool, go to
   "Share Resource Tree Administration Wizard" -> "Edit Shared Resource Tree" -> "Explore SRT"
   Then check the Folder <SRT>\Symantec\Sre\DriverStore\ whether it is having any inf named folder with VMXNET3 drivers or not.

For better understanding about "BMR Physical machine to virtual machine restore" process refer below videos
https://www-secure.symantec.com/connect/videos/netbackup-bmr-701-release-windows-2008-client-physical-machine-virtual-machine-restore-part1
https://www-secure.symantec.com/connect/videos/netbackup-bmr-701-release-windows-2008-client-physical-machine-virtual-machine-restore-part2
Mark_Solutions
Level 6
12 years ago
Dont forget for dissimilar restores that you need to edit the client BMR configuration and add in the MAC address of the target server against each required interface for it to actually work
Harsha_Kumar
Level 2
12 years ago
Thanks every one for help, Issue is resolved.

We have problem with the VMXNET3 adapter drivers,

we have to select the E1000 drives for the VM, since the Vmxnet3 does not support to discover the network, updated the drivers E1000 instead of vnet3.

There are couple of ways to update the drivers in ESX server

we can download the drivers and update in driver package or select the drivers in ESX server as E1000 instead of vmxnet3 drivers for network adapters.

Here is the KB from the VMWare website to update in ESX server.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003020

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805

Here is the link from the Symantec Team.

http://www.symantec.com/business/support/index?page=content&id=TECH181674

http://www.symantec.com/connect/forums/bmr-restore-no-network-interface-were-discovered

Forum Discussion

BMR on windows 2008 R2

5 Replies

NetBackup-BMR 701 release: Windows 2008 client Physical machine to virtual machine restore (Part1)

https://www-secure.symantec.com/connect/videos/netbackup-bmr-701-release-windows-2008-client-physical-machine-virtual-machine-restore-part1

Windows Device Driver Requirements for Bare Metal Restore (BMR)

Bare Metal Restore best practices and recommendation?

BMR implementation

Related Content

BMR restore from Physical Windows Server 2008 to Virtual Windows Server 2008

BMR restore.

BMR - failed to create bootable iso image Windows

NetBackup Master Server Migration from Windows 2008 R2 to Windows 2012 R2 or Windows 2016 R2

BMR Boot server service not starting in windows server 2008 ent 64bit