Recovery Manager for Exchange and AppAssure when Restoring an Exchange 2013 machine. (4212702)

You are running AppAssure Core on Windows 2012 Standard edition that protects an Exchange 2013 agent. AppAssure reports no issue in protecting the agent and all mountability/checksum checks complete successfully.

AppAssure is able to protect the agent and mount the data on the Core while using Quest Recovery Manager to recover mail data on the Exchange 2013 database; however, the Quest Recovery Manager fails with an exception error.

You will see the following error:

Manager. The attempt fails while trying to load the Exchange database in Quest Recovery Manager. The Windows

Application Log shows Multiple Ese errors and warnings, including Event ID 455 Error 455 (StoreHost64(3400) Error -1811

(0xfffff8ed) occured while opening logfile <Path>\<log_base>.log) [ie. c:\ProgramData\Mounts\...\czflbjxjk\E02.log]

AppAssure is not officially supported with use of Recovery Manager for Exchange. The below workaround has been known to work successfully, however if you run into any issues with this process there may be no other suggestions at this time.  

WORKAROUND

1. Mount the Recovery Point of the Exchange 2013 agent database in the AppAssure Core as "Mount Writable"

Note: If you do not mount the database as "Mount Writable" then you will get an error when trying to rename the log file in Step 2.

2. Access the mounted agent database on the disk where the MountPoint databases are located and rename Exxtmp.log to Exx.log.

E.g. E01tmp.log needs to be renamed to E01.log

3. Open the Quest Recovery Manager for Exchange console and add an offline Exchange database

4. Browse the location of the Exchange 2013 agent database (.edb) and select it. RME will then find the log file from step 2 on its own.

5. Select the restore point date you wish to restore based off the .edb and log file you added.

Note: in Step 5, RME has been known to retrieve multiple dates in the Select a Restore point. It has been known to work with the most recent date selected in this screen.

6. Click Next and you will now find your Exchange 2013 database available in Storages of the left pane of Recovery Manager for Exchange.

If the above steps do not resolve the issue, there is an issue with the database headers and the recovery point. At this point, you will need to run a repair on the database using eseutil /P.

 STATUS

Enhancement Request TF00298652 has been submitted to Development for consideration in a future release of Recovery Manager for Exchange.