Data Protection Manager (DPM) 2010 is Not Performing a Server State or Bare Metal Recovery Backup

I have a dedicated Backup Server (2008 R2) running System Center Data Protection Manager 2010. I am trying to backup another Server 2008 R2 system. Everything is working great except the System State and Bare Metal Recovery backup. I consistently get the following message: "Replica is inconsistent" for both protection group members. It has not worked since installed and the disk allocation is reporting way more than enough allocated space to back each of them up. Windows Server Backup was running previously and had no issues what so ever.

Any ideas what I am missing?
Who is Participating?

Improve company productivity with a Business Account.Sign Up

rsoly777Connect With a Mentor Commented:
In case of BMR protection, DPM uses Windows Backup to directly write to the DPM replica (unlike in the case of System State backup, where Windows Backup dumps to a local volume and DPM then moves it to the replica).

This failure could mean that the DPM replica is out of space.

Do you see an alert on the DPM monitoring pane that says that the replica is out of space?

Alternatively, if you have auto-grow turned on, DPM will automatically grow the replica when required.
take a look at this it looks just like the same issue you are explaining:
This alert is generated when the replica of the specified volume on the DPM server is inconsistent with the data source. All protection activities for the data source will fail until the replica is made consistent with the data source by performing synchronization with consistency check.
Possible causes for an inconsistent replica include:
•      The consistency check that DPM automatically performs on a newly created replica during replica creation has not yet been performed.
•      The synchronization log on the file server ran out of space before all data changes to the data source were logged.
•      DPM determined that the file server shut down unexpectedly.
A consistency check must be performed on the specified replica.
If a daily consistency check is scheduled, DPM will automatically perform the consistency check at the next scheduled time. For more information, see How to modify protection options. Otherwise, you need to manually perform a consistency check on the replica. For more information, see How to synchronize a replica.
If the average synchronization log disk usage is 75 percent or greater, you should allocate more disk space for the synchronization log. This will minimize the risk of inconsistent replicas. For more information, see How to modify disk allocation.
miopeaAuthor Commented:
I have done automated (twice daily) and manual consistency checks. When I do a manual consistency check the following occurs:
When I right-click on the error and select: "Perform Consistency Check"
Then: Status goes to "OK" for a second.
Then: "Replica is inconsistent, verification in progress..." for a few seconds.
Then: Status goes back to "OK" for a second,
Then: Status goes back to original error: "Replica is inconsistent"

re: Synchronization log disk usage determination:
The link above is for DPM 2006. I am using DPM 2010. The instructions break down at Steps #4 and #5 below:
To determine if a synchronization log is running out of disk space
   1. In the DPM Administrator console, click Protection on the navigation bar.
   2. Select the protection group associated with the synchronization log.
   3. In the Actions pane, click Modify disk allocation.
   4. In the Recommended disk allocations table, click Change. <There is no "Change" option>
   5. The Space to allocate for synchronization log box displays the current disk allocation for the synchronization log.  <I don't see this at all>
   6. Compare the allocated disk space with the log usage data in your report to determine if the synchronization log is running out of disk space.

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

See if this helps:

This error normally occurs due to one of the following two possible causes:

    * Not enough disk space is available on the protected machine to store a backup of the system state files
    * The Windows Server Backup feature is not installed on the protected machine

The latter is an easy one to solve; simply install the required feature onto the protected machine from Server Manager. Installation of this feature doesn’t normally require a reboot.

If the protected machine doesn’t have enough disk space to store a backup of the system state files (you’ll need 10-12Gb free on the system drive by default to store these files), you’ll need to create some space on the system drive, or add another disk to the machine and modify the PSDataSourceConfig.xml file to allow DPM to use the new location. The PSDataSourceConfig.xml file is normally located at %SystemDrive%\Program Files\Microsoft Data Protection Manager\DPM\DataSources. Modify the <FilesToProtect> section of the xml file to point to the new drive added. Note that you may need to remove protection for the machine from the DPM 2010 console and then re-enable protection to get DPM to read the new location for backup files from the PSDataSourceConfig.xml file.

miopeaAuthor Commented:
My apologies for my late response..priorities pulled me away.
rsoly777: Thank you for the added detail, but it did not solve the problem, although I did not change anything:
1. Windows Server Backup feature was previously installed and did a bare metal and server state backup no problem
2. I have 52.7 GB free on system drive of protected server

I think I would try to remove protection for the machine from the DPM 2010 console and then re-enable protection to get DPM to re-read the location for backup files from the PSDataSourceConfig.xml file.
miopeaAuthor Commented:
I had also done this previously. I increased the total backup storage drives and had decided to remove all protection and start over. The result was the same: everything works OK except Bare Metal and Server State.

Status:      Replica is inconsistent
Replica path:      Click to view details  <see details below>
Latest recovery point:      -
Oldest recovery point:      -
Total recovery points:      0
Disk allocation:      Replica volume: 62.50 GB allocated, 91.29 MB used | Recovery point volume: 6.56 GB allocated, 61.54 MB used

These are the error details:
server-main = protected computer
Source (Protected Server):     Computer\System Protection\Bare Metal Recovery on

Destination (DPM server):      c:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_98deb076-fe2f-480c-ae25-2ed73bda86c7\63c878c4-603c-4c7b-81b2-22308afeaa7b\Full\F-Vol\

Drive c: on DPM server has 95GB free
have you tried uninstalling and re-installing windows server backup? Everything I see out there seems to relate back to this and this also appears to be a known issue that appears to not have been properly adressed by Microsoft yet. May be worth using ms support if it is available to you.
My DPM server doesn't show the Bare Metal Recovery option inside "System Protection" for some clients. Please advice
miopeaAuthor Commented:
This situation has finally been resolved. I had tried everything I could think of: un-sintalls, re-installs, new locations, nothing worked. On the server I was trying to do the BMR/SS backups, I ran Windows Server Backup (which ran fine with no errors).When Windows Server Backup had finished, it showed the total amount of data backed up on C: and D: (the two physically connected drives required to be backed up for a BMR/SS backup), but the listing for BMR and SS had a dash through the amount of data backed up...? I then went back to my DPM backup server and manually increased the disk allocation for the BMR member to equal the protected server storage space used by Windows Server Backup for Drive C: and D: on that server. I did the same for the SS member. The DPM backup then worked fine for BMR and SS backup on the protected server.

I guess I don't understand the following:

1. Drive C: and D: volumes had always backed up OK and show the same amount of space used for the DPM backup as Windows Server Backup showed after it's local backup on the protected computer. Why did I have to allocate more amount space for the BMR member and then again for the Server State member?

2. After the DPM backup of the protected server BMR and SS was completed, the reported disk space used for each was identical to the other and yet each was larger that C: and D: combined. Why would that be? What exactly is being backed up by BMR and SS that is not already on Drive C: and D:?

3. Why didn't the "Auto Grow" feature work on the BMR and SS backups?

miopeaAuthor Commented:
I had to increase the space again (I went double the size of C: and D: combined). It now seems stable. The place to look for the out of space error turned out to be on the protected volume as Windows server backup was attempting to do the backup (Thank You for that tip rsoly777), determined there was not enough space on the DPM server, errored out, and DPM did not know why and hence did not have a chance to auto-grow. This explains why there was to "not-enough-space" error in the Monitoring section of DPM. However, the Windows Server Backup log showed the problem.

Since this technically was a space issue,
miopeaAuthor Commented:
Add to Solution: Check the windows Server Backup logs on the protected server.
miopia glad this all worked out
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.