Symptoms
- Protection group member displays “Replica is Inconsistent”
Troubleshooting
There is a large number of reasons you could be seeing this error, the two main areas to focus on are making sure that the backup feature is installed and the event viewer logs on the target server
Resolution 1
- Right click on the member and click “Perform consistency check…”
Resolution 2 (Server 2012 and 2008 R2)
- Connect to target server
- Open PowerShell window
- Type “import-module servermanager”
- Type “get-windowsfeature”. this will display a list of the Windows Services and Features that are currently installed
- Locate the Windows Server Backup line and ensure that it is ticked, if not continue with this resolution
- (Server 2012) Type “add-windowsfeature windows-server-backup”
- (Server 2008 R2) Type “add-windowsfeature backup”
- Right click on the member in the DPM console and click “Perform consistency check…”
Resolution 3 (Server 2008)
- Open Server Manager
- Click Add Features
- Locate Windows Server Backup Features and expand
- Select Windows Server Backup and click next, then finish the wizard
- Right click on the member in the DPM console and click “Perform consistency check…”
Resolution 4 (Server 2003)
- Install the Server 2003 VSS update http://support.microsoft.com/kb/940349
- Right click on the member in the DPM console and click “Perform consistency check…”
Resolution 4
- Verify that the volume that you are attempting to backup has enough HDD space, general rule is to have the volume (when OS volume) at 50% capacity but this can vary depending on your individual requirements
Resolution 5
- Open CMD as administrator
- Type “wbadmin -destination <dest>” where <dest> is the location that you wish to backup everything to, e.g. D:\Backup (WARNING: this will use up a large amount of space)
- Right click on the member in the DPM console and click “Perform consistency check…”
Thanks for the windows backup tip, this seemed to help for my secondary DPM server
Same here, resolution 2 worked for our 2008R2 server 🙂
Thanks for the info. I thought I’d just add that in our case the problem ended up being that we were running DPM 2012 SP1 and it was getting these types of errors because we were trying to back up stuff off of a 2012 R2 Hyper V cluster. Apparently there are some compatibility issues. We upgraded to DPM 2012 R2 and backups of the VMs off the hyperV hosts are working fine again.
It’s actually a nice and helpful piece of information. I am glad that you shared this helpful info with us. Please keep us up to date like this. Thanks for sharing.