none
Backup Active Directory System State always failed RRS feed

  • Question

  • Hi,

    I have tested several scenario/customer to perform backup Active Directory System State. However DPM 2010 always failed and keep mentioned "Inconsistent Replica" . If i check on recovery point, it is indicated 0 and i'm assume initial replica has failed as well. Anything extra that i need to do to solve this issue?

    pls advise


    laiys
    Tuesday, January 18, 2011 9:51 AM

Answers

  • Just to re-enforce and give more details on what MikeR is saying.

     

    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:

    If the error isn't self expainatory, 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 succesfull 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

     

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, January 22, 2011 7:28 PM
    Moderator

All replies

  • Hi,

    DPM 2010 uses a command for windows backup to do a system state backup.

    Most of the time, when there are issues, it is because of:

    - Not enough storage on the server of which you want to take a backup of

    - Something wrong with Windows Backup

    - VSS writer that has an issue.

    To troubleshoot this, could you:

    1) Do a vssadmin list writers on the AD server

    2) See in the eventviewer on the AD server if there is an error from windows backup

    3) If you didn't modify the configuration file for the DPM agent, then let us know how much storage your "c:\" drive is and how much there is left (to check for the storage issues)

    Let us know

    Brgds,

    Mike Resseler

     

     


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Tuesday, January 18, 2011 2:01 PM
    Moderator
  • Just to re-enforce and give more details on what MikeR is saying.

     

    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:

    If the error isn't self expainatory, 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 succesfull 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

     

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, January 22, 2011 7:28 PM
    Moderator