none
System State Replica is Inconsistant RRS feed

  • Question

  • My W2003 32-bit DPM 2007 Tape Backup failed for the first time in more than three years.  I blieve it is due to a failed system state on the two W2008 64-bit) servers (Server A & Server B) it is backing up.  These servers were recently (upgraded to vmware servers about a month ago, but have been working for at least 4 weeks).  I found a couple of posts for these two errors.  I changed the Replica Volume from 15Gb to 20 GB on both to no avail.  I searched all of the *.errlog for "is Incompatible" and found nothing on the DPMserver.

    Below is what I found in the DPM Event viewer:

     

    Event Type: Error
    Event Source: DPM-EM
    Event Category: None
    Event ID: 1
    Date:  3/14/2011
    Time:  9:33:20 AM
    User:  N/A
    Computer: DPMServer
    Description:

    The replica of SystemState on ProtectedserverA.domain.net is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3163)
    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)


    DPM ID: 2^|^DPMserver^|^Replica inconsistent^|^DPM^|^Backup^|^ProtectedserverA.domain.net^|^7a2c5c5a-ebc3-4988-95ed-9285ee3f14c6

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: DPM-EM
    Event Category: None
    Event ID: 1
    Date:  3/14/2011
    Time:  9:33:13 AM
    User:  N/A
    Computer: DPMserver
    Description:

    The replica of SystemState on ProtectedserverB.domain.net is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3163)
    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)


    DPM ID: 2^|^DPMserver^|^Replica inconsistent^|^DPM^|^Backup^|^ProtectedserverB.domain.net^|^4ac4ef12-ae9e-4147-9247-07e46c0066a6

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    Peter Jam

     

    ran vssadmin just in case:

    C:\Windows\System32>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {b272cd73-5fc8-4eae-b22f-b698c37417cd}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {1052cae0-6c3e-4c16-b7d8-77e46598cabf}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {1daf9de2-c925-4dba-a592-d4adbf4a78cb}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {5fca2d50-1ddc-43ed-b02f-f3633312e713}
       State: [1] Stable
       Last error: No error

    Writer name: 'DFS Replication service writer'
       Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
       Writer Instance Id: {ad3eca4a-91b1-42c2-87e5-b8215f370c72}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {ef94be92-1e51-4ccf-970b-aac4a98fd405}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {c68164b2-56ce-4e11-a93c-4cb77bb7e85d}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {d7432004-c210-4ac6-9862-39c806087df6}
       State: [1] Stable
       Last error: No error

    • Edited by pjamme Monday, March 14, 2011 7:38 PM renamed DPMserver
    Monday, March 14, 2011 2:49 PM

Answers

  • Hi,

    The error suggests that you don't have enought free space on the protected server to hold the systemstate backup.  Check free space on C: - you need ~15GB free, then run this command from an administrative command prompt and see if it displays any additional errors:

           wbadmin.exe start systemstatebackup -backuptarget:C:


    The backup logs are located in 'C:\Windows\Logs\WindowsServerBackup

    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

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, March 14, 2011 11:27 PM
    Moderator
  • Hi

    Yes,  DPM is the victim here, please open a thread in the Windows backup group concerning the wbadmin errors.

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

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


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by pjamme Wednesday, March 23, 2011 2:23 PM
    Tuesday, March 15, 2011 3:25 PM
    Moderator

All replies

  • Hi,

    The error suggests that you don't have enought free space on the protected server to hold the systemstate backup.  Check free space on C: - you need ~15GB free, then run this command from an administrative command prompt and see if it displays any additional errors:

           wbadmin.exe start systemstatebackup -backuptarget:C:


    The backup logs are located in 'C:\Windows\Logs\WindowsServerBackup

    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

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, March 14, 2011 11:27 PM
    Moderator
  • Mike:

    Thanks for your help.

    I had changed the Replica Volume from 15Gb to 20 GB on both protected servers prior to posting to no avail.

    This is the PSDataSorceConfig.xml on Server B:

    <?xml version="1.0" encoding="utf-8"?>
    <PSDatasourcesConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/2003/dls/PSDatasourceConfig.xsd">
     <DatasourceConfig>
      <WriterId>8c3d00f9-3ce9-4563-b373-19837bc2835e</WriterId>
      <Version>01.00.0000.00</Version>
      <VssWriterInvolved>false</VssWriterInvolved>
      <LogicalPath>Computer</LogicalPath>
      <ComponentName>SystemState</ComponentName>
      <FilesToProtect>E:\WindowsImageBackup\*</FilesToProtect>
      <Size>10240</Size>
      <UseDRWithCC>true</UseDRWithCC>
     </DatasourceConfig>
    </PSDatasourcesConfig>


    Drive E:\ has 274GB free

    ServerB C:\Windows\Logs\WindowsServerBackup is empty?? Drive C:\ has 21.7GB free

     

    this is the result of the run as administrator command.  first I got Wbadmin.exe is not a valid Win32 application and when I said OK I got Access is denied.  I changed to the Windows directory and got:

    Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\slospjam-A>wbadmin.exe start systemstatebackup -backuptarget:C:
    Access is denied.

    C:\Users\slospjam-A>cd\

    C:\>cd windows

    C:\Windows>wbadmin.exe start systemstatebackup -backuptarget:C:
    'wbadmin.exe' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Windows>

     

    I will look over document bb809015 and report back later.

     

     


    Peter Jam
    Tuesday, March 15, 2011 12:27 PM
  • Hi

    Yes,  DPM is the victim here, please open a thread in the Windows backup group concerning the wbadmin errors.

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

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


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by pjamme Wednesday, March 23, 2011 2:23 PM
    Tuesday, March 15, 2011 3:25 PM
    Moderator
  • Thanks Mike

    I'm on my way.


    Peter Jam
    Tuesday, March 15, 2011 3:30 PM
  • Mike,

    Windows Server Backup was not an installed Role.  All is fine now.  Thanks again.


    Peter Jam
    • Proposed as answer by zMottie Wednesday, August 17, 2011 5:36 AM
    Wednesday, March 23, 2011 2:23 PM