troubleshooting Question

Unable to restore mailbox database in exchange 2007

Avatar of kmkj4ever
kmkj4ever asked on
ExchangeActive DirectoryStorage Software
10 Comments4 Solutions1437 ViewsLast Modified:
Recently we had our exchange 2007 server fail. Reinstalled exchange on a new server and attempted to restore the mailbox database to a Recovery Storage Group with Backup Exec 12.5 The restore seemed to work until I attempted to mount the database.

Received the following error when trying to mount the restored database in the EMS TA.:

Error encountered while trying to mount the database

Error encountered while trying to mount the database (Mailbox Database) in the recovery storage group (Recovery Storage Group). error message is Exchange is unable to mount the database that you specified. Specified database \WIN2K8-EX\Recovery Storage Group\Mailbox Database; Error code: MapiExceptionCallFailed: Unable to mount database (hr=0x80004005, ec=1276)

In the event viewer I see the following errors:

Event 1088, MSExchangeIS
The information store could not be loaded because the distiguised name (DN /O=LAN/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN= of message database "Recovery Storage Group\Mailbox Databe" does not match the DN of directory /O=FIRST ORGANIZATION/OU=EXCHANGE ADMINISTRATIVE GROUP(FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=.
The database may have been restored to a computer that is in an organization or site different than the original database.

Event 9519, MSExchangeIS
Error 0x4fc starting database "Recovery Storage Group\Mailbox Database" on the Microsoft Exchange Information Store.

Event 9518, MSExchangeIS
Error 0x4fc starting Storage Group /DC=COM/DC=LAN/CN=Configuration/CN=
Service/CN=Microsoft Exchange/CN=First Organization/CN=Administrative Group/CN=Exchange Administrative Group  (FYDIBOHF23SPDLT)/CN=Server/CN=WIN2K8-EX/CN=Information Store/CN=Recovery Storage Groupon the Microsoft Exchange Information Store.
MDB failed to start

I have search the web with various articles talking about scanning and repairing the database, but as far as I can tell the database is cleanly shutdown. It looks like the errors point to a difference in the organization name from the old server to the new server.

Any help you could provide would be greatly appreciated.

Kevin B
ASKER CERTIFIED SOLUTION
kmkj4ever

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 4 Answers and 10 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 4 Answers and 10 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros