none
DPM 2012 R2, EX2007SP3, and EX2013CU5 Coexistence Scenario - Failure to Backup Both Sources to 1 DPM Server RRS feed

  • Question

  • All, I've got the following Exchange Coexistence Scenario that I'm attempting to backup:

    Exchange 2007 SP3 RU12 - 2 MBX CCRs, 5 MBX standalones

    Exchange 2013 CU5 - 1 DAG with 6 nodes, all multirole

    And I am attempting to back it up with:

    DPM 2012 R2 (KB3009516 update applied) - 1 DPM server with storage and tape library installed, 1 SQL server (dedicated)

    The problem that I'm running into is that as part of the Exchange backup prerequisites it's stating that I need the latest ESE.DLL and ESEUTIL.EXE that exist in the environment, but I'm running into errors backing up 2007 when I have the 2013 ESE.DLL and ESEUTIL.EXE files in the BIN directory, and errors backup up 2013 when I have the 2007 files in the BIN directory - and obviously since they're named the same, they can't both exist at the same time!

    Does anyone know of a workaround for this without me having to dedicate another piece of hardware - along with storage - to backup this environment?

    The sad part is that I can manually swap out the files and back either one up - and if I have to do that... well, someone should have figured out a better solution to this a long time ago.

    Sunday, November 16, 2014 7:46 PM

All replies

  • Hi,

    Historically - the latest versions of ese.dll and eseutil.exe have always been backwards compatible so that you can protect multiple versions of exchange with a single DPM server.  It looks like the exchange group broke tradition and the exchange 2013 version is only backwards compatible with Exchange 2010.

    I will raise this issue up the flag pole and see if exchange has plans to resolve the incompatibility.


    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, November 20, 2014 3:46 AM
    Moderator
  • Hi,

    Historically - the latest versions of ese.dll and eseutil.exe have always been backwards compatible so that you can protect multiple versions of exchange with a single DPM server.  It looks like the exchange group broke tradition and the exchange 2013 version is only backwards compatible with Exchange 2010.

    I will raise this issue up the flag pole and see if exchange has plans to resolve the incompatibility.


    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.

    Awesome, thank you.

    Phil H.

    Thursday, November 20, 2014 5:03 AM
  • So just circling around…

    I had an exchange engineer test a 2013 eseutil.exe and it worked just fine against a 2007 database.

    What issues are you having exactly when eseutil.exe is ran against the exchange database and log files after a recovery point is made.


    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.

    Monday, January 19, 2015 5:49 AM
    Moderator