Performing a Bare Metal Restore with DPM 2010 - The Official System Center Data Protection Manager Team Blog - Site Home - TechNet Blogs

Performing a Bare Metal Restore with DPM 2010

Performing a Bare Metal Restore with DPM 2010

  • Comments 23
  • Likes

Toolbox So, you’ve protected your server with BMR using DPM and now you need to restore. What's next?

Well, I’ve been playing with the new BMR functionality on DPM 2010 for a while now and while it is very slick in how it operates, it seems like there might be some confusion on exactly how to use it. Granted, creating a BMR backup of a server is quite simple, restoring requires a little bit of extra work outside of the scope of DPM.

I’m not here to talk about what BMR is or when to use it instead of system state as that information is covered on the DPM TechNet Site. I’m more concerned with restoring a BMR backup to a new system.

Since theoretically the system in question is completely down (due to corruption of the operating system) or even new (in the case of hardware replacement), I have discovered is that the easiest way to restore these systems is by booting to the Windows media (Windows 2008 or Windows 2008 R2 DVD) and initiating the recovery.

IMPORTANT If you use a domain in your environment, and if the backup storage location is on a computer that is a member of that domain, then the computer containing the storage location should be on the IPsec boundary to be accessible by non-domain computers. When a computer boots into Windows Recovery Environment, it becomes a non-domain computer and cannot access the usual network shares. Only those computers that allow non-domain computers to access the share can be used as a backup storage location in this way.  You can also address this issue by adding the computer that is your backup storage location to a workgroup and placing the backup in a shared folder. A computer running Windows Recovery Environment behaves as if it is in a workgroup, enabling you to access the shared folder with the backup.

This will break down into two steps. Step one is done on the DPM server and step two will be performed on the system where the restore will take place. It looks like a lot of steps, but really it’s quite simple so give it a shot some time! Test it out to be sure you understand before you are hit with the need for it and don’t know how to get it to work.

Step 1 – Recover contents of WindowsImageBackup folder (the easy part):

1. In the DPM administrator console, navigate to the Recovery tab and navigate through the Protected data to the computer you need to restore and find the Bare Metal Recovery option:


2. Select the date and time and then select Recover…The Recovery Wizard should start:


3. Recover this data to a network share:


4. Select a destination for the copy. Note the space required in my case is 13.22 GB. There MUST be enough free space at the destination for the copy to be successful:


In this case I chose the E drive:


5. Select to apply the security settings of the destination computer and then click Next:


6. Verify the summary information, then select “Recover”.


7. The recovery process is taking place. If you wish you can verify the progress via the monitoring tab:


8. Since we are going to be recovering to a network share (a folder on a computer that is protected by this DPM server), we will need to go to that location and create the folder where the restore will happen.  Select that location and finish then restore.

Remember, this is just restoring the files to a location for use by the recovery process.  This will not do any of the work to restore the files onto the actual computer. Also note, as pointed out before, you need to access this location when booted into the WinRE environment from the DVD. This means WinRE must have generic network access (get an IP address) and you must be able to specify valid credentials to access that share and files below it.

9. This is an IMPORTANT step here! Navigate to the location the files were restored to and navigate down the restored folders until you find the folder where the backup is stored.  The important note here is that you must share the folder above WindowsImageBackup so that at the root of the shared folder is the WindowsImageBackup folder. If that is not at the root then the restore will not find the backup.  This is what it will look like and where the share will be created:


This is the share that will need to be connected to by the client using WinRE. If you feel like I may be beating this dead horse, well I am. It is vital to create the share that you will be able to get to in WinRE (IP connectivity and authentication) and that the WindowsImageBackup folder is on the root of the share. (If I could attach flashy red lights to a blog, they would be around this step).

Note: There are some locales that will create the restore folder with a trailing period. You will need to remove this before sharing it out or you will not be able to connect to the share.

To resolve this issue, on the computer where the files were restored, open an administrative command prompt and navigate to the folder right before the folder ending with a period.

C:\BMR\DPM_5-11-2011_20.19.29> dir

Volume in drive C has no label.
Volume Serial Number is 1245-8090

Directory of C:\BMR\DPM_5-11-2011_20.19.29

11.05.2011 12:10 <dir> .
11.05.2011 12:10 <dir> ..
11.05.2011 12:10 <dir> DPM_Recovered_At_5-12-2011_12.10.52.odp.

Rename the DPM_Recovered_At_5-12-2011_12.10.52.odp. folder to DPMRecovery.  Note that you must use the short name of the folder to accomplish this:

C:\BMR\DPM_5-11-2011_20.19.29>ren DPM_Re~1 DPMRecovery

C:\BMR\DPM_5-11-2011_20.19.29> dir

Volume in drive C has no label.
Volume Serial Number is 1245-8090

Directory of C:\BMR\DPM_5-11-2011_20.19.29

11.05.2011 12:10 <dir> .
11.05.2011 12:10 <dir> ..
11.05.2011 12:10 <dir> DPMRecovery

The folder \DPMRecovery can now be navigated to and shared out as needed.

Step 2 – Restore the files from the WindowsImageBackup folder to a computer (these steps are based on the premise that you can get an IP address and authenticate via WinRE in your environment)

1. Start the computer you are going to restore the image to using the Windows DVD to match the system you are restoring. If you are doing BMR for a Windows Server 2008 system, then boot to the Windows Server 2008 DVD. If you are doing BMR for a Windows Server 2008 R2 system, then boot to the Windows Server 2008 R2 DVD.  On the initial screen, verify language/locale settings and click Next.:


2. When the Install screen comes up, select Repair your computer in the lower left of the screen (most people move past this screen quickly so it’s easy to miss).


NOTE: If you need to verify the number or size of disks needed to restore, look in the WindowsImageBackup folder for MBRsystemRequirements.txt file. You should see information similar to the following:


Minimum number of disks: 1
Minimum Disk Sizes: Disk 0: 64423526400 bytes (boot)

3. You now have the System Recovery Options screen. This may list an existing OS if it finds one on the drive. We are going to be looking to do a restore, so we are not worried if there is one listed.

For Windows Server 2008, just click Next.

For Windows Server 2008 R2, be sure that you select the radio button to Restore your computer using a system image that you created earlier before selecting Next.

5. This step is ONLY ON Windows Server 2008: When prompted to choose a recovery tool, select Windows Complete PC Restore:


6. You will now likely be prompted that Windows cannot find a system image, select Cancel.

7. On the next window select “Restore a different backup.”


7. It will now prompt you that you need to point it to an image.

For Windows Server 2008, select Restore different backup and then Next.

For Windows Server 2008 R2, select Select a system image and then Next.

8. This will bring up a screen allowing you to find the image you are going to restore from. Since we have put this on a network share, we need to start networking. To do this, click on Advanced:


9. This brings up a screen that will allow us to search the network.

On Windows Server 2008, choose Search for a backup on the network:


On Windows Server 2008 R2, choose Search for a system image on the network.

10. When prompted if you are sure, click Yes.

11. Now enter the path to the share created in step 8 from Step 1 – Recover contents of WindowsImageBackup folder:. You can also connect using the IP address and share name. Click OK:


12. This will prompt you for credentials needed to access the share. Enter the credentials required for the share and click OK.

13. Now it will show a list of recovery images available from the share you indicated. There should only be one as you shared out only the recovery point specific for this computer. Select that recovery point from the list and click Next:


14. This will now scan the backup you selected for specific backups available in that recovery point. This again should yield just one date/time stamped recovery and list the hard drive associated with it. Select this recovery point and click Next:


15. Check the box to have it Format and repartition disks in order to have it wipe out the local disks before laying down the restore, then click Next:


16. Finally, verify the settings and click Finish to have it begin the restore process:


17. You will then get a confirmation:


18. After clicking OK you will see the progress as it takes place:


Once done the machine will reboot.  Bing-Bang-Boom, your system is back up and running just like it never happened. This is such a beautiful thing and as long as you are protecting Windows Server 2008 or Windows Server 2008 R2, you can say goodbye to SRT! Sleep well tonight knowing your servers are just a quick 45 minute restore away.

Chris Butcher | Senior Support Escalation Engineer

clip_image001 clip_image002

Bookmark and Share

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Ok, so this sounds all cool, and I have DPM 2010 up and running and am getting use to the new features.

    I actualley setup a server just the other day and selected the BMR and SS backup options. They backup, but within seconds after a syncronization the status changes to 'Replica is Inconsistent' and no recovery point has been setup.

    The servers file system and the SQL instance on it all have recovery pionts and are working just fine... any ideas? I was kind of looking forward to testing it out...

  • Since it sounds like it is failing immediately and never getting the initial replica, the problem is usually with the server you are protecting.  The easiest thing to look for is that the protected server (PS) does not have the Windows Server Backup (WSB) feature installed.  Just look on the PS features and install the WSB feature.

    If that is installed already, then you will have to troubleshoot why WSB may not be functioning as expected.

    Hope this helps.


  • Chris,

    Thanks that's what is was, WSB wasn't installed. We missed that step. Got it installed and now it's working just dandy. Migth try a restore later on this week.

  • Hi,

    I ran a BMR restore on a windows xp workstation from the DPM 2007 and it took around 4 hrs to complete the full restore. How much time does it take for an average recovery?

  • With DPM 2010, you can only do a BMR backup/restore on Windows 2008 or Windows 2008 R2.  There is no support for system state or BMR on any client SKUs.  With that said, when going through the BMR restore process, the actual restore for me has only taken 30-40 minutes.  This of course is based on my environment, but the bottom line is the restore itself it relatively quick.

    I haven't had a chance to play with the DPM 2007 implementation, but I would assume it should go about the same.  The BMR restore process is outside of DPMs ability at that point as it just puts the bits down and the OS (WinRE in this case) takes care of the restore.

    Hope that helps answer some of your questions.


  • What is the logic for having no support for client SKU's?

  • Hi Chris,

    First of, nice post. I do have a question which I've tried to answer (or find an answer) but with no success. So when you do a BMR backup of your Windows Server 2008 Domain Controller, is AD and Cert stuff included in there, or do I have to do a System State Backup as well if I ever needed and wanted to restore my Domain Controller. DPM says its included in System State but does not mention anything about BMR.



  • Hello Eric.  Sorry for the delayed responce.  These are posted by someone (JC) for us, so we don't have notifications if there are comments and I just happened by to see your comment today.  The answer to your question is that BMR includes system state, so you can use a BMR backup to either restore just system state, or the full drive with BMR.  BMR uses wbadmin to determine critical drives and any drive that has AD information on it will be flagged and included in the backup.  So, the short answer is that you will be able to do a system state or full restore of your DC if you have protected it with BMR.

    @ Sejong - I don't know for sure, but I believe the logic for not allowing any client SKU's is that they are usually just imaged and the data can be protected separately and thus people will likely not want to spend the money on a full liscense to protect them that way when they can just reimage the box and then restore the data for just the cost of a client liscense.

  • i got this error when connecting to shared location

    An internal error occurred the following information might help you resolve the error

    The network name cannot be found (0x80070043)

  • I have tried to get an answer to this for a while but I havent managed to find people with the correct knowledge i guess.

    How do i perform a BMR from a hyper-v virtual server to a metal server ?

    I get a blue screen saying the hardware has changed too much, but is there some workaround to that ?

  • +1 on Daniel's comments. How do we restore from physical to virtual, or from virtual to physical?

  • How do I configure the NIC settings and IP address on the trashed server from this environment on the OEM DVD ?

  • I protect the system state and c: vole of two servers with DPM 2010.  I'm looking for a script to restore the System state to a network share so I can schedule it every envening as part of my DR strategy.

    I have a script compiled but it just seems to hang.



    $pgList = Get-ProtectionGroup -dpmServerName Livdpm01 | where {$_.FriendlyName -match "forefrontBareMetal"}

    $DSList = @()

    ForEach ($pg in $pgList)


    $DSList += @(Get-Datasource -protectionGroup $pg)


    ForEach ($DS in $DSList)


    #Get the latest recovery point.

    $recoveryPoints = @(Get-RecoveryPoint -datasource $DS | sort -property RepresentedPointInTime -Descending)

       if ($recoveryPoints.Length -eq 0)


           Write-Host "No recovery point available for" $DS.Name -ForeGroundColor Yellow



       $latestRecoveryPoint = $recoveryPoints[0]

       $RecoverableItem = Get-RecoverableItem -RecoverableItem $latestRecoveryPoint -BrowseType child | where { $_.UserFriendlyName -eq "Bare Metal Recovery" }

       $rop = New-RecoveryOption -targetServer $targetServerName -recoveryLocation CopyToFolder -SystemProtectionDataSource -TargetLocation $restorePath -RecoveryType Restore

       Recover-RecoverableItem $RecoverableItem -recoveryoption $rop


  • Hello,

    excellent post. Do I understand it correctly that Bare Metal Recovery contains ALL data from the protected server? Let's assume this is a virtual vmware box with only C: drive. Does restoring BMR get you to the point where all data is in place and you can fire up your box, or you still need to restore file backup for entire C: drive?


  • Hello,

    I follow the instructions to perform a BMR to my domain controller (windows 2008 R2) but after the new hardware boots all services (active directory, DNS etc) are down and failing. Any special that i should do to my Domain Controller before back up or after restore to new hardware?