Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Weird recovery situation - not able to open RSG mailboxes using Exmerge

Posted on 2010-01-12
Medium Priority
Last Modified: 2012-05-08
This is a weird situation, so let me explain first:  The system is Exchange 2003 on Windows Server 2003 (both Standard edition). I was requested by a client to recover a mailbox from a backup tape that is 2+ years old. The Exchange server that was backed up onto this tape no longer exists in the organization. The backup was created using Backup Exec 9.1, which the firm is still using.  The software allows you to redirect a RSG restore to a different server, provided that there is a storage group/database on that server with the original name. So, I moved all of the active mailboxes off one of our Exchange servers to the other, deleted the storage group/mailbox store and created a new one named "Mailbox Store (SERVER)", with (SERVER) being the name of the old server. I then created an RSG on this server and was able to redirect the restore from the tape to the RSG.  It appeared to restore successfully, although I had to run a repair on the database after restore.  The database mounts fine, but all of the mailboxes show as "disabled" (i.e., with a red "X").

Now comes the Exmerge part. I'm trying to use Exmerge to export just the single mailbox that I need.  However, Exmerge fails with the message "Error opening message store (MSEMS)" which usually indicates a permissions issue. However, I've double- and triple-checked all of the permissions, and the account I'm using definitely has Full Control permission for both the RSG and the active mailbox database on this server.

One additional quirk of this situation is that the user has an active mailbox currently on a different server than the one I'm using for the recovery.  Is this perhaps causing the issue? I can't create a mailbox for that user on the server that I'm trying to use for the recovery, nor can I move her active mailbox to the recovery server, since one of the requirements of this situation is that the user can't be aware of the fact that this material is being recovered.

Any help/ideas would be greatly appreciated.
Question by:Hypercat (Deb)
LVL 12

Expert Comment

ID: 26300718
LVL 38

Accepted Solution

Hypercat (Deb) earned 0 total points
ID: 26306438
For future reference, I found the solution through posting to the Microsoft partner forums.  The problem was that the recovery database was pointing to the old server name as the original mailbox database location, so Exmerge couldn't connect to the original mailbox during the export process.  Here are some articles explaining the process and how to fix it to work when your original database location no longer exists:
How the Recovery Database Links Back to the Original Database
How to Change the msExchOrigMDB Attribute Using ADSI Edit


Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Stellar Exchange Toolkit: this 5 in 1 toolkit comes loaded with mega-software tool. Here’s an introduction to tools’ usage and advantages:
In this post, I will showcase the steps for how to create groups in Office 365. Office 365 groups allow for ease of flexibility and collaboration between staff members.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

571 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question