[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1510
  • Last Modified:

Using an EDB file from a failed Exchange 2010

Hello experts,

One of the mailbox servers in our organization has failed. We have the only database EDB file. Is it possible to attach it to another server and connect the mailboxes?
0
Muhajreen
Asked:
Muhajreen
  • 5
  • 4
  • 4
2 Solutions
 
MuhajreenAuthor Commented:
I forgot to say that our environment is using Exchange 2010
0
 
chakkoCommented:

Take a look at this:

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2975-Mailbox-Recovery-Exchange-2010.html

There are also 3rd party software tools which can access the EDB file directly and export to PST files.
You can search for them.
some are PowerControls from Ontrack (I have used with success) or
http://www.nucleustechnologies.com/Exchange-Server-Data-Recovery.html
0
 
MuhajreenAuthor Commented:
Thanks a lot for your quick reply

Now I understood what happened exactly. An administrator has deleted all the .log files from the mailbox database folder to save disk space because drive was full and server was not responding.

In the article you sent above, it says that log files should be restored.

Are log files mandatory and required ? If so, Is there any solution for us?
0
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 
chakkoCommented:
In general, I think you can get away with the log files.  All of the email should have been committed to the mail database already.

The worst that can happen is you may be missing some recent email from the log files.
 So, No you don't really need the log files.

0
 
pritamshCommented:
MuhaJreen,

Is database in clean shutdown state if yes move all log files to different location and mount database.

Else try recover database using recover exchange mode , this will help you mount database.
0
 
MuhajreenAuthor Commented:
Database is now dismounted. When I try (Mount Database) through EMC, I receive this error:

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Failed to mount database 'Mailbox Database 1993646385'.

Mailbox Database 1993646385
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database 1993646385; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)
.. [Database: Mailbox Database 1993646385, Server: EXCHANGE2.ourdomain.com].

An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)
.. [Database: Mailbox Database 1993646385, Server: EXCHANGE2.ourdomain.com]

An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)
. [Server: Exchange2.ourdomain.com]

MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)



--------------------------------------------------------
OK
--------------------------------------------------------
0
 
chakkoCommented:
also, since the disk filled up because of log files, that means that your backup is not working.  After a successful backup of Exchange the log files should be flushed from the system (removed).

I would suggest you make a backup of the edb and exchange folders before proceeding.  
0
 
pritamshCommented:
Muhajreen,

if database is in clean shutdown state you should be able to mount is sucessfully else execute eseutil /r for repairing you database.
0
 
MuhajreenAuthor Commented:
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Bin>eseutil /r

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Usage Error: Missing logfile base name specification.

Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API parameter) after 0.16 seconds.
0
 
pritamshCommented:
0
 
MuhajreenAuthor Commented:
Thank you both for the great help ! The database has been repaired and the server is working well now.
0
 
chakkoCommented:
In the folder where the log files should be located.  the log related files should have prefix E##
there is also the .chk checkpoint file.

I can't remember the exact functions (been some time since I had to use these).  But If you have log files and the .chk file you should try to move those to a new location (outside of that folder).  Then try to start the Information store and mount the database.

If you still get an error you need to use eseutil as the URL provided by pritamsh.  

also the command to check if the database is in a dirty shutdown state is eseutil with the /mh option
Dirty state can prevent the database from mounting

0
 
pritamshCommented:
Chakko,

if database is in clean shutdown state moving log files will help, it is something dial tone database recovery but if database is in dirty shutdown then you need to run multilple eseutil switches like /MH /ML / K for checking database consistency and depending upon corruption you might need to run /R or /P.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 5
  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now