Video Screencast Help

BMR restore is showing below error

Created: 27 Mar 2013 | 8 comments

Hi need updates over this issue

In Bmr restore when i perform prepare to restore i am getting below error

V-126-74 Please make sure that the configuration package for at least one device of type:Network inteface card

I ahve attached  the screen shot of error  below.Kindly provide solution as soon possible

Operating Systems:

Comments 8 CommentsJump to latest comment

mandar_khanolkar's picture

This would indicate mainly that you do not have Windows Recovery environment compatible device driver available in your BMR driver repository.

What is your client OS being recovered? Architecture 32/64 bit? Which NB client server version you are using?



Kushaal's picture

We are doing restore physical machine over virtual machine.
NBU client :7.5.3

mandar_khanolkar's picture

Yeah, that is a scenario of dissimilar system recovery where destination machine device drivers needs to be available within BMR driver repository.

Please check below video which I had uploaded explaining exactly the same use  case you are trying to execute. That will explain you the required steps in detail.

Link to Full Demo Video on SymConnect

Link 1:

Link 2:



Kushaal's picture

Hi used the same windows to erform this activity.

IN my case i had to perform BMR restore on Hyper -V virtual mchine

We have clustered master server 

foe ex

server in cluster virtual IP

After following the same video i could not perform prepare to restore operation


I created the SRT on 225 and iso also on 225 

IN my case master is itself a Boot server.

But  I am not able to perform SRT or iso from 228

Yasuhisa Ishikawa's picture

Masterserver can be culstered, but other role including BMR boot server can not be clustered. So you can not configure boot server as 228.

For Prepare to Restore issue, please post detailed steps and screen shot of each step.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

mandar_khanolkar's picture

For BMR on Hyper-V, you may want to follow below tech-note instructions.


  1. BMR Restore on Hyper- V virtual machine fails to provide mouse or keyboard access in the restore environment.
  2. BMR Restore on Hyper-V virtual machine fails to detect a Virtual Hard disk.
  3. BMR Restore environment on Hyper-V virtual machine fails to detect the virtual network adapter.


On a Hyper-V virtual machine, BMR restore process needs to communicate with synthetic or emulated devices. The new architecture of synthetic devices with Hyper-V poses some unique challenges for system administrators. Without the integration components, users are required to move their VHD's around to the IDE controller, which limits the amount of VHD's that can be used at any given point in time. Additionally, legacy network adapters might need to be added to the VM to provide network access. Also the mouse and keyboard do not work.

However, by adding the integration components to a Windows PE image, those are no longer concerns. The Integration Components of Hyper-V are a set of drivers that are a significant performance change that you can apply to virtual machines for them to be able to install synthetic devices instead of emulated devices.

Some of the drivers that are installed using the Integration Components are: Video driver, network driver (with this you avoid using Hyper-V’s Legacy Network adapter), storage driver, VMBUS (transport for synthetic devices), time sync (time synchronization with the host), etc


  1. Download and install the Windows Automated Installation Kit (AIK) 1.1

Note: Size of WAIK is quite big. You can contact Symantec Support to get smaller and required footprint of this SDK.

2.   We need to extract two files from the c:\windows\system32\vmguest.iso file, which is part of Hyper-V RC1 (available at

You can also mount the ISO image in a VM and extract the files as well. We’re looking for two files. Copy the file that is appropriate for your architecture:

  • 32 Bit: \support\x86\Windows6.0-KB951633-x86.msu
  • 64 Bit: \support\amd64\Windows6.0-KB951633-x64.msu

           At times there are .CAB files present instead of the MSU. Copy the file  

          that is appropriate for your architecture at a folder ---- MSUSOURCE


3.  Create a directory by name “IC” on the same system you installed the AIK, and store the file(s) above there.

4. Expand the CAB file within the directory: %MSUSOURCE%\IC\Drivers

5. Copy the SRT WIM image SRT.WIM and SRT_x64.WIM to a temporary directory ---   PESOURCE

6. Create the folder where you are going to mount the WIM image. “C:\Temp\mount

7. Mount the WIM file using imagex tool:

imagex  /mountrw “%PESOURCE%\srt.wim” 1 “C:\Temp\mount”

imagex  /mountrw “%PESOURCE%\srt_x64.wim” 1 “C:\Temp\mount

8. Inject all drivers one by one using PEIMG tool considering the SRT and driver architecture:

      peimg  /inf= %MSUSOURCE%\IC\Drivers\x86\*.inf /image=”C:\Temp\mount

peimg  /inf= %MSUSOURCE%\IC\Drivers\amd64\*.inf /image=”C:\Temp\mount

*.inf is representing all the previous drivers that we added above. Repeat the command line for each file.

9. Commit changes:

imagex /unmount /commit C:\Temp\mount.



Kushaal's picture

Hi Is it possible to perform BMR restoration of a system when source from which BMR backup
iwas taken is alive

mandar_khanolkar's picture

you can do it but needs change in environment especially to resolve client name <-> ip-address, like,

If original machine is up then NB master server would resolve client name -> ip-addr to this original host and not the one under recovery. So you may need to change master server settings to resolve client name to different IP-address. Obviously this different ip-address needs to be set in client's BMR configuration by taking copy of "current" config. You can change NB master and media server hosts file to hard-code this temporarily.

In case you do not change ip-address of client BMR config then recovery would fail due to duplicate ip-address settings in the same subnet.