I came across this issue while trying to perform a consistency check on a Windows Server 2008’s system state. You will see the below alerts in the DPM Console.
“The replica of System State ComputerSystemState 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 (ID 3106).
“DPM failed to create the system state backup. If you are trying to create the system state of a Windows 2008 Server operating system, verify that the Windows Server Backup (WSB) is installed, and that there is enough free disk space on the protected server to store the system state. (ID 30214 Details: Internal error code: 0x809909FB).”
The reason we need space on the machine that is getting backed up, is because DPM creates the system state file on the local machine and then backs up the file it created.
If you only have one drive on the protected server then your only option is to clear down space on the drive. However if you have an additional drive, then we can make the System State file be created on another drive which has enough free space.
To do this follow the below steps.
To change the location of the system state backup file
- On the protected computer, open PSDatasourceConfig.xml in Notepad. (File located in “<Drive Letter>:Program FilesMicrosoft Data Protection ManagerDPMDatasources”.
- Change the <FilesToProtect> value from %systemdrive% to the desired location.
- Save the file.
- On the DPM server, if there is a protection group protecting the system state of the protected computer in step 1, run a consistency check.
- The consistency check will fail and generate an alert. Perform the recommended actions in the alert as follows:
- In the alert details, click the Modify protection group link, and then step through the wizard. This may fail again but continue to the next step.
- Perform a consistency check.
Then create a recovery point to disk and then it should start to synchronize.