Unable to configure BMR protection on Windows Server 2008 from DPM 2012 r2 server RRS feed

  • Question

  • We are trying to implement BMR and System State protection on our physical servers and have had issues when trying to set it up for a server running windows server 2008. I have verified that the DPM agent is up to date running version 4.2.1273.0. When configuring the protection group and expanding system protection the only option is system state. When configuring protection on other physical servers running Windows Server 2012 I am able to select bare metal recovery. Has anyone else had this issue and know how we can resolve this? Thank you for anyone who takes the time to lend a helping hand.
    Tuesday, December 16, 2014 6:06 PM

All replies

  • Hi,

    From following article, BMR of Windows Server 2008 is supported from DPM 2012 R2 with Update Rollup 2


    As you did not mentioned the exact update version please check if it is related. 

    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, December 17, 2014 8:14 AM
  • Thank you for the reply Shaon. I have looked into this and found that we are updated to UR4 or KB3009516. The resource your provided does show that this type of protection on a 2008 server should be possible.
    Thursday, December 18, 2014 7:50 PM
  • Hi,

    Do you have Windows backup feature installed on the server in question?  Also is the server part of a work group or untrusted domain?

    Information for protecting computers in workgroups and untrusted domains:



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

    Friday, December 19, 2014 1:02 PM
  • Hi SHSupport,

    was this issue fixed?

    Tuesday, March 10, 2015 5:37 PM