Im hoping you would be able to help me out with this little problem Im having. I installed DPM 2010 in our test environment to test backups on Exchange 2010. Restore a server with Bare Metal Recovery protection in DPM 2. R2. Bare Metal Recovery BMR enables you to make a full protection of a machine. Usually BMR is used on servers. Thanks to BMR, even if a server crashes, you can restore it from a recovery point. The main advantage of BMR is that the restoration is performed very fast. In the example of this post, the restoration of a virtual domain controller is accomplished in 1. In this post we will see how to restore a server with Bare Metal Recovery protection in Data Protection Manager 2. R2. The server to restore is a virtual domain controller on Windows Server 2. Do you want to make backups FROM that share, or TO that share If you want to make backups FROM that share, install the DPMagent on the server hosting. Adding backup storage. Installing and configuring DPM and Azure Backup. ProtectionAgentInstallationWizard03.png' alt='How To Install Dpm Agent On Server' title='How To Install Dpm Agent On Server' />R2. Previously I have made a full system protection of this server. For this example, servers are named as below Protected server VMADS0. DPM server VMDPM0. There are two steps to restore a server with BMR protection Recover a BMR backup. Restore a server with Bare Metal Recovery. Recover the Bare Metal Recovery. A28B0A.png' alt='How To Install Dpm Agent On Server' title='How To Install Dpm Agent On Server' />First of all, I verify that VMADS0. I need at least one recovery point for this test. So the below screenshot shows you that replica of VMADS0. So lets go to recover the Bare Metal Recovery. First open the Recovery tab. In Browse field, enter the name of your server. OtsRDL7VOCQ/ToYty0JXLLI/AAAAAAAAASo/PDxI6TUqKJc/s1600/dpm14.png' alt='How To Install Dpm Agent On Server' title='How To Install Dpm Agent On Server' />Choose a recovery point with the calendar. Boson Ccna Test Cracked more. Once you have chosen a recovery point, right click on Bare Metal Recovery as below, and select Recover. On the first screen of recovery wizard, just click next. Because I have no tape library, I want to copy recovery files to a network folder. How To Install Dpm Agent On Server' title='How To Install Dpm Agent On Server' />So the recovery will be performed across the network. On specify destination screen, click on Browse and choose where you want store the recovery files. I choose VMDPM0. 1 on D Restore folder. Next configure recovery options as you want. You can for example set the network bandwidth uses for recovery needs, an E mail notification or security option. Once all parameters are set, click on Recover to copy files where you have specified. During the recovery process, you can view the state on Monitoring tab. Once the recovery process is finished, you should have a recovery success alert. Open the folder where are located recovery files and rename it with a shorter name. This is to ease the recovery process in the next steps. Create a share on your recovery folder. Now that recovery files are hosted and ready to be used, we will see how to use the restore files from server side. Restore a server with Bare Metal Recovery. First, insert ISO of your operating system to boot on the Windows Server installer. For me, the OS is Windows Server 2. R2. Choose your language as fresh OS installation. Next click on Repair your computer. Then click on Troubleshoot. Click on System Image Recovery. The below warning is normal. Because my machine has no data on its hard disk, no system image is stored. So just click cancel. So click on Select a system image. Click advanced to take recovery files from a network share. Enter the network folder. For my example the network folder is VMDPM0. BMRMy. Computer. So the backup is listed. Select it and click next. Select what you want to restore and click next. In this section you have additional options. For example you can restore only one disk or install additional drivers. Click on finish to launch the restoring of your system. In barely 1. 0 minutes, my server is restored. Because this server is a domain controller, I have checked about the behaviour of the replication process. It is impressive because the Active Directory service knows that a restoration took place and so it ask a replication from its friends As you have seen, the restoration process is pretty easy and fast so Bare Metal Recovery protection is a good way to protect servers. However the main disadvantage of this protection type is that it uses a lot of storage space because all data are saved. But I am ready to lose some storage space for this awesome protection. DPM 2. 01. 0 System Protection Job fails because backup location unwriteable. We have a Server 2. R2 DC that runs as a virtual machine on a vmware host. We back this up using DPM 2. Recently the backup started failing and the error on the DC is The backup operation that started at 2. T0. 7 5. 1 5. 0. Z has failed because the remote shared folder BMCBAC0. Please make sure user SYSTEM has write permissions for this location, and then rerun the backup operation. There is enough free space on the client to hold the backup image. If I look in the share and storage management section of file services I can see that share is marked with a red x. Clicking properties against that item throws the error 8. Program FilesMicrosoft DPMDPMVolumesReplicaNon VSS Datasource Writervole. FullC Vol Cannot verify that the folder exists. Illegal characters in path. Ive reinstalled the agent and removed and readded the machine from the protection group all TNAAny help appreciated. UPDATE I see in this thread that an MS person has said that the illegal characters in path error is normal. So we need to concentrate I guess on event ID 5. Backup with text as above. On the machine in question vssadmin list writers shows no writers with errors. C Windowssystem. Volume Shadow Copy Service administrative command line tool. C Copyright 2. 00. Microsoft Corp. Volume path Volume6. Volume name Volume6. Volume path C. Volume name Volume6. I note that the volume here doesnt match that on DPM but Im guessing that isnt the issue.