BMR backups re completing Partial

[BVshet]

Hi Team,

We have a Physical serverith win 2012 OS and the BMR backups are getting partial and in job details see below error.

17/05/2015 22:33:04 - Error bpbrm(pid=16156) BMRERR: Received BMR error: An error occurred while processing driver for PCI\VEN_14E4&DEV_1657&SUBSYS_169D103C&REV_01\4&E1128B4&0&0010, Please verify driver installation.The driver for HP Ethernet 1Gb 4-port 331FLR Adapter is not compatible with Windows PE. You may need to create a driver package that is Windows PE compatible to restore this system using Bare Metal Restore.The driver for HP Ethernet 1Gb 4-port 331FLR Adapter is not compatible with Windows PE. You may need to create a driver package that is Windows PE compatible to restore this system using Bare Metal Restore.The driver for Emulex LightPulse HBA - Storport Miniport Driver is not compatible with Windows PE. You may need to create a driver package that is Windows PE compatible to restore this system using Bare Metal Restore.The driver for Emulex LightPulse HBA - Storport Miniport Driver is not compatible with Windows PE. You may need to create a driver package that is Windows PE compatible to restore this system using Bare Metal Restore.The driver for Smart Array P420i Controller is not compatible with Windows PE. You may need to create a driver package that is Windows PE compatible to restore this system using Bare Metal Restore.The driver for Smart Array P420i Controller is not compatible with Windows PE. You may need to create a driver package that is Windows PE compatible to restore this system using Bare Metal Restore. (1)

Is there a link where we can check copatibility of windows PE and drivers, moreover if drivesr are not compatible then ho is server up and working fine.

Kindy help,

Bshet.

[sdo]

It maybe something similar to:

https://www-secure.symantec.com/connect/forums/bmrsavecfg-error-device-incompatible-windows-16-pe

.

...but even if it's not similar, the post above has steps that you can use to collect the bmrsavecfg logs, which may reveal what your problem is.

Perhaps, you could try collecting the logs, and reviewing them.  And if you can't see what the problem is then attach the logs to this thread - and someone may have time to go through them.  (N.B: Please do not post logs as post/thread text - instead please attach/upload them to this thread.)

[Jaime_Vazquez · Accepted solution]

In order to better diagnose the matter, the 'bmrsavecfg" debug log is required reading. Use this TECH article to assist with debugging of error code 1 BMR enabled backups.

BMR enabled backup jobs fail with status code 1
http://www.symantec.com/docs/TECH207639

After running the command "bmrsavecfg -infoonly" execute the command "echo %ERRORLEVEL%" to get the status code of the command.  I left that out in the original article.

Later version of NBU and BMR should be showing messages that a specific driver is incompatible with any older version of WinPE image, such ".. is incompatible with WinPE Version 1.6". .

This article will be of help as well in describing the driver needs for BMR recoveries:It to is in need of some minor "tweaking" for latest BMR releases.

Windows Device Driver Requirements for Bare Metal Restore (BMR) 
http://www.symantec.com/docs/TECH181674

You also have to understand that a WinPE environment is not the same as a fully installed OS version running on a client system. The WinPE environment used by BMR runs entirely out of a RAMDISK, not a physical disk.

[Jaime_Vazquez]

I  want to add that the OS version of the client system is not associated with the version of WinPE in use by BMR at recovery time. The WinPE version in use by a BMR SRT is related to the version of BMR on the Master/Boot Server, not the client.All BMR SRT instances are basically generic and will allow recovery of any Windows OS version that is supported by that  release.