none
The replica of Volume D:\ on server is not consistent with the protected data source. DPM error ID = 93. (ID 33123) RRS feed

  • Question

  • We are deploying SC 2012 DPM to backup the network and one of our servers won’t do the initial synchronization. I am getting the following error over and over (every hour)

    There is currently no info on this error on Microsoft (http://technet.microsoft.com/en-us/library/hh858776.aspx)

    ------------------------------------------------------

    Type:     Synchronization

    Status:  Failed

    Description:        The replica of Volume D:\ on server is not consistent with the protected data source. DPM error ID = 93. (ID 33123)

                    More information

    End time:             11/14/2012 6:00:06 AM

    Start time:           11/14/2012 6:00:06 AM

    Time elapsed:    00:00:00

    Data transferred:             0 MB

    Cluster node      -

    Source details:  D:\

    Protection group:            File Servers

    ------------------------------------------------------

    Status:  Replica is inconsistent

    Replica path:      Click to view details

    Latest recovery point:    -

    Oldest recovery point:   -

    Total recovery points:    0

    Disk allocation:  Replica volume: 1,579.96 GB allocated, 139.10 MB used | Recovery point volume: 254.36 GB allocated, 97.68 MB used

    ------------------------------------------------------

    This server was being backed up by DPM 2012 Rollup3 and we just upgraded to SP1 Beta as not all of the data off of our Server 2012 servers were getting backed up. Now, it is not backing up at all.

    I have upgraded the client on the server but it will not start the sync.

    The C: Drive, System State and Bare Metal Recovery are backing up correctly, just the D: and E: drives (where the data is) is not getting backed up.

    Please advise.


    • Edited by Keith Hummel Wednesday, November 14, 2012 4:57 PM
    Wednesday, November 14, 2012 4:31 PM

Answers

  • Hi,

    We do not support protecting Windows Server 2012 using SCS DPM 2012 until after SC SP1 is released which is still in beta.   Please do not expect any support for DPM 2012 running on Windows Server 2012, or issues while protecting data sources in Windows Server 2012.

    With that said, you need to run a consistency check before normal synchronizations will work.  If the Consistency check fails, you need to troubleshoot based on the error of the failure.  Post the failed CC job and if it's something obvious we can help you.


    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.

    • Marked as answer by Keith Hummel Wednesday, November 14, 2012 5:29 PM
    Wednesday, November 14, 2012 5:22 PM
    Moderator

All replies

  • Hi,

    We do not support protecting Windows Server 2012 using SCS DPM 2012 until after SC SP1 is released which is still in beta.   Please do not expect any support for DPM 2012 running on Windows Server 2012, or issues while protecting data sources in Windows Server 2012.

    With that said, you need to run a consistency check before normal synchronizations will work.  If the Consistency check fails, you need to troubleshoot based on the error of the failure.  Post the failed CC job and if it's something obvious we can help you.


    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.

    • Marked as answer by Keith Hummel Wednesday, November 14, 2012 5:29 PM
    Wednesday, November 14, 2012 5:22 PM
    Moderator
  • Yea, I realize that it is not supported yet.

    Looks like I need to upgrade our backup server from 2008 R2 to 2012

    Type: Consistency check
    Status: Failed
    Description: DPM is attempting to back up or restore a deduped file, which requires Deduplication to be enabled on backupserver. (ID 30241 Details: Internal error code: 0x80990AD0)
    More information
    End time: 11/14/2012 9:25:40 AM
    Start time: 11/14/2012 9:24:29 AM
    Time elapsed: 00:01:11
    Data transferred: 0 MB
    Cluster node -
    Source details: D:\
    Protection group: File Servers
    Items scanned: 0
    Items fixed: 0

    Wednesday, November 14, 2012 5:29 PM
  • Hi,

    Yes, that is correct, the volume you are attempting to protect is on a Windows 2012 server and you have enabled the Dedupe feature.  Only DPM 2012 Sp1 running on a Windows 2012 server can protect that workload.


    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.

    Wednesday, November 14, 2012 5:32 PM
    Moderator
  • I saw this post and decided to reply. We are currently running Server 2008 R2 receiving the same error message.

    Type - Recovery Point
    Status - Failed
    Description - The replica of System Protection Computer\System Protection on <server name.FQDN> is not consistent with the protected data source. DPM error ID = 93.
                         (ID 33123)
    End Time - 3/6/2013 8:00:01 PM
    Start Time - 3/6/2013 8:00:01 PM
    Time Elapsed - 00:00:00
    Data Transferred -
    Cluster Node -
    Recovery Point Type -
    Express Full
    Source Details - Computer\System Protection
    Protection Group Members - 2
    Protection Group - <server name> - System State

    What I am currently not sure on and I may have to fix the first two before this stage will work, the "Consistency Check" and "Replica Creation" also failed. Once I get those two issues resolved will the "Recovery Point" work?

    Thursday, March 7, 2013 2:45 PM
  • Christopher,  This seems to systemstate protection.

    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, March 7, 2013 5:10 PM
    Moderator