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.

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.

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.

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.