HELP!!! System Center Data Protection Manager 2012 R2 - BMR & System State Replica is inconsistent...
Hi, I am hoping someone can clear the muddy water for me.
I have SCDPM 2012 R2 running and am actually backing up a few production (physical) servers at the moment. All Protection Status state OK...EXCEPT the "Computer\System Protection\Bare Metal Recovery" & "Computer\System Protection\System State" protection groups, which display "Replica is inconsistent".
I have read several online articles pertaining to this issue and have installed the "Windows Server Backup" feature only, not the Windows Server Backup Feature - Command-line Tools, because none of the articles stated it, only the WSB feature.
I even tried disabling the WinRE agent and re-enabling it.
I still receive the same status after Performing consistency checks at every change.
When I check the servers being backed up (Protected Servers) event logs, I noticed it mentions being out of space for the backups.
There was another article I recently read that mentioned this out of space alert and stated to resolve the issue you need a separate shared drive on the DPM server to store the BMR & SS backups to for the Protected Servers and that each server would require 40GB of space. This seems crazy and I just need clarification to get to the bottom of this issue.
Can someone clear all this up for me and help me figure out what I am missing to resolve this issue with my Protection Group backups?
Also, does anyone know if SCDPM 2016 address this issue?
Thanks in advance.
I have SCDPM 2012 R2 running and am actually backing up a few production (physical) servers at the moment. All Protection Status state OK...EXCEPT the "Computer\System Protection\Bare Metal Recovery" & "Computer\System Protection\System State" protection groups, which display "Replica is inconsistent".
I have read several online articles pertaining to this issue and have installed the "Windows Server Backup" feature only, not the Windows Server Backup Feature - Command-line Tools, because none of the articles stated it, only the WSB feature.
I even tried disabling the WinRE agent and re-enabling it.
I still receive the same status after Performing consistency checks at every change.
When I check the servers being backed up (Protected Servers) event logs, I noticed it mentions being out of space for the backups.
There was another article I recently read that mentioned this out of space alert and stated to resolve the issue you need a separate shared drive on the DPM server to store the BMR & SS backups to for the Protected Servers and that each server would require 40GB of space. This seems crazy and I just need clarification to get to the bottom of this issue.
Can someone clear all this up for me and help me figure out what I am missing to resolve this issue with my Protection Group backups?
Also, does anyone know if SCDPM 2016 address this issue?
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This was the resolution to my issue.
1. In the Application Event Log, what DPM related warning or error events are being logged? Can you post the events?
2. What does the disk allocation look like for the Protection group? Is Grow Automatically enabled?
3. What does the disk allocation utilization look like for the BMR object for the protected server?
4. What does the disk allocation utilization look like for the System State object for the protected server?
5. How many volumes (drives) are in the protected server?
6. Have you tested running WBADMIN directly on the server to see if a System State or BMR fail locally on the server?
6a. SS: wbadmin start systemstatebackup -backuptarget:<PlaceYourTa
6b. BMR: wbadmin start backup -allcritical -backupTarget:<PlaceYourTa
Trouble Shooting DPM: https://blogs.technet.microsoft.com/dpm/2011/10/31/troubleshooting-data-protection-manager-system-state-and-bare-metal-backup/
This is a great article that covers most issues that I've come across when dealing with the same issue.
Dan