Hi,
We have in place here a DPM server, running 2012 SP1 on a Server 2012 box. Physical.
Connected to it is an iSCSI set of disks and an HP LTO4 tape drive, that we use for B2D then tape, all of these are working fine.
The backup has been running fine on it for ages, but the other day I spotted a failure on one of our file shares. Upon closer inspection it had been failing for a few days! All our files are on a 2012 file server cluster, connected to our SAN.
Within DPM i get the "Replica is inconsistent" message, if i try and preform a consistency check, it goes away and says fine, it then reports back within 30mins and the error is back, no jobs are run during this time. If i manually try and create a recovery point it errors immediately with Error 208, "no recovery point was created, either because synchronization has not occurred since the last recovery or because no changes were found."
I then get the following error in the monitoring tab.
"Affected area: H:\ Description: The replica of Volume H:\ on is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency
check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
DPM failed to synchronize changes for Volume H:\ l because the snapshot volume did not have sufficient storage space to hold the churn on the protected computer (ID 30115 Details: VssError:Insufficient storage available to create either the
shadow copy storage file or other shadow copy data.
(0x8004231F))"
Now, the only thing to have changed was dedupe was turned on for that drive. But as per the setup DeDupe is also installed on the DPM server.
Does anyone know what the cause might be, or how to fix. If I can't fine one soonish, we are going to have to turn off DeDupe i guess to go back to what we had working!