none
DPM cannot create a backup because WSB on protected computer encountered an error RRS feed

  • Question

  • I was installing DPM 2010 on a Windows Server 2008 R2 machine and I am having problems with some recovery points. When I try to run a "synchronization job with consistency check" on computer system states DPM fails with the following error:

    Affected area:    Computer\System Protection

    Description:    The replica of System Protection Computer\System Protection on computer.example.com 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 cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 546, WSB Error Code:  0x8078011D). (ID 30229 Details: Internal error code: 0x809909FB)

    On the protected computer the event log show the following errors:

    Event ID 1000

    Faulting application nmccollector.exe, version 0.0.0.0, time stamp 0x48078d22, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000374, fault offset 0x00000000000aef37, process id 0x9fc, application start time 0x01cb1eb3f2e95fe4.

    Event ID 546

    Backup attempted at 'date & time ' failed to start, error code '2155348253'.

     

    Windows Server Backup is installed on the protected server and shares and databases are successfully backing up with no problem.

    Thanks For Your Help!

    -Pete

    • Moved by Praveen D [MSFT] Monday, July 19, 2010 6:28 AM Moving to DPM SS and BMR Protection Forum (From:Data Protection Manager)
    Friday, July 9, 2010 1:09 PM

Answers

  •  

     

    DPM relies on Windows backup to create the systemstate, so if the windows server has probems that prevent Windows backup from running successfully, you need to fix that first.

    To help troubleshoot systemsstate backup run the following from an administrative command prompt.

        wbadmin.exe start systemstatebackup -backuptarget:C:

    Please leverage the Windows backup forum http://social.technet.microsoft.com/Forums/en-US/windowsbackup/threads to help troubleshoot:


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, July 9, 2010 6:33 PM
    Moderator

All replies

  •  

     

    DPM relies on Windows backup to create the systemstate, so if the windows server has probems that prevent Windows backup from running successfully, you need to fix that first.

    To help troubleshoot systemsstate backup run the following from an administrative command prompt.

        wbadmin.exe start systemstatebackup -backuptarget:C:

    Please leverage the Windows backup forum http://social.technet.microsoft.com/Forums/en-US/windowsbackup/threads to help troubleshoot:


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, July 9, 2010 6:33 PM
    Moderator
  • Please re-open if the above post do not help in resolving the issue.
    Thanks, Praveen D [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, November 20, 2010 6:16 PM