cannot backup Exchange 2019 databases with SCDPM2019 RRS feed

  • Question

  • I was trying to use SCDPM2019 with 3 Exchange 2019 databases.

    After creating a protection group for 2 Exchange 2019 servers with 3 databases, that group was created successfully.

    But after creating the first replica on DPM, I'm always getting this error:

    I copied eseutil.exe from Exchange 2019 to DPM - so both versions are the same.

    I even dismounted all 3 databases, checked with eseutil their consistency - everything OK - deleted all logs and system files and mountet the databases again. That way I'm absolutely sure that Exchange is consistent…   After that I deleted on DPM the protection group - and deleted all files on disk - and created a new protection group with the same 3 Exchange databases. Unfortunately that didn't help - same error…

    Any ideas?


    FG Clodt


    Sunday, March 29, 2020 3:36 PM

All replies

  • Here the missing error message:

    Mailbox Database xyz
    2903.2020 162241
    The replica of Exchange Mailbox Database Mailbox Database xyz on 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)
    Data consistency verfication check failed for LOGS of Exchange Mailbox Database Mailbox Database xyz on (ID 30146 Details: Unknown error (DxcDDD0135) (DxCDDD0135))
    More information
    Either the database files are corrupt or the proper Versions of the Eseutil.exe and Ese.dll files are missing.
    If you have recently upgraded Your Exchange server, Copy them from that server to the DPM server. Contact Your Exchange server administrator, and then verify the issue. You can recover the last known good backup to address the corrupted state.
    Synchronize With consistency check.
    Run a synchronization job With consistency check...
    To dismiss the alert, Click below


    Sunday, March 29, 2020 3:41 PM
  • Hi fgclodt,

    It's Exchange forum here and we focus on Exchange issues. Do you have any problems with Exchange?

    Usually, we recommend to use Windows Server Backup to back up and restore Exchange data, for detailed information, refer to this link:

    It seems you are talking about an issue with SCDPM2019, I suggest you to post your issue in Data Protection Manage forum for better support.

    Thanks for your understanding.


    Eric Yin

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact

    Monday, March 30, 2020 7:57 AM
  • Hi,

    Could you provide some more information about your DPM and Exchange environments?

    • Operating system version for DPM & Exchange servers.
    • SQL Server version of your DPM database.
    • Disk type of your Exchange databases (NTFS / ReFS).
    • Is this a Database Availability Group (DAG) or not?

    Best regards,

    Blog: LinkedIn:

    Monday, March 30, 2020 8:25 AM
  • Hi Leon,

    here the details:

    - Operating Systems: all Windows Server 2019 Desktop Edition 1809

    - SQL:  2017 Standard Edition with Reporting Services

    - Disk Type:  all NTFS

    - DAG: No




    Monday, March 30, 2020 8:30 AM
  • Did you follow every step mentioned in the guide below, and also install all prerequisites in the correct order?

    Back up Exchange with DPM

    Blog: LinkedIn:

    Monday, March 30, 2020 8:38 AM
  • I checked once more - but looks good.

    But I may restart from the beginning...




    Monday, March 30, 2020 9:28 AM
  • Give it another try, clear the logs before and follow the steps accordingly, let us know how it goes!

    Blog: LinkedIn:

    Monday, March 30, 2020 10:01 AM