locked
DPM 2012 SP1 Failing consistency check on System State RRS feed

  • Question

  • Hello,

    Recently just upgraded our DPM 2012 to SP1 and on our exchange server the system state remains inconsistent.  Here is the error logs.

    The replica of System Protection Computer\System Protection on EXCHANGE.DOMAIN 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 create the backup. If you are backing up only System State, verify if there is enough free space on the protected computer to store the System State backup.  On protected computers running Windows Server2008, verify that Windows Server Backup (WSB) is installed and that it is not performing any other backup or recovery task. (ID 30214 Details: Internal error code: 0x80990ED0)

    Wednesday, January 23, 2013 7:10 PM

Answers

  • Hi

    DPM uses Windows backup to create a systemstate. Please check the protected server (PS) and make sure the Windows backup feature is installed and if already installed look for any event messages on the PS for Windows backup that may detail the cause of the failure.

    Run this command from an administrative command prompt and see if it displays any additional errors:

           wbadmin.exe start systemstatebackup -backuptarget:C:


    Backup logs are located in 'C:\Windows\Logs\WindowsServerBackup

    If the error isn't self-explanatory, please open a thread in the Windows backup group concerning the wbadmin error.

    http://social.technet.microsoft.com/Forums/en-US/windowsbackup


    Once Wbadmin can take a successful systemstate backup, DPM systemstate backups should succeed.


    NOTE: System state backup using wbadmin could be working for you may be because you have selected backup target which has lot of free space. In the DPM case this drive may not be the one that is being used. To find out which drive DPM is using to stage the system state backup, can you open "C:\Program Files\Microsoft Data Protection Manager\DPM\Datasources\PSDataSourceConfig.xml" and check the free space on the drive that is present in <FilesToProtect> tag.

    You can change the drive location as appropriate and re-configure protection for system state.

    See http://technet.microsoft.com/en-us/library/bb809015.aspx


    Also be sure that whatever size the  WindowsImagebackup folder is on the protected server that the replica volume is equal or greater.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, January 31, 2013 10:26 PM