We help IT Professionals succeed at work.

Exchange DB not mounting after h/w issue

bruce_77
bruce_77 asked
on
Hi

Running Exchange 2007 SP2 on Windows 2008 SP2 SCC Active/Passive cluster.

We had an issue with our SAN today and some LUN's were powered off hard. When the issue was resolved, we remounted the databases but one won't mount.

I get an error message saying that transaction logs are missing. I ran eseutil MH which says the DB is in dirty shutdown. The logs required are

0x34701-0x3470b

The weird thing is, I can actually see these log files in the transaction log LUN.

Does anyone know any commands I can use to

i. Check whether these files have been corrupt?

ii. Force the database to replay these

Comment
Watch Question

Solutions Architect
Top Expert 2016
Commented:
run eseutil and isinteg

http://www.msexchange.org/tutorials/exchange-isinteg-eseutil.html
http://technet.microsoft.com/en-us/library/aa998249%28EXCHG.80%29.aspx


meanwhile, you need to get back i will recommend to run dial tone restore

http://technet.microsoft.com/en-us/library/bb310773%28EXCHG.80%29.aspx


if you cant get it working, you need to use 3rd party software to restore like ontrack software
http://www.krollontrack.com/data-recovery/e-mail-recovery-software/
Madan SharmaConsultant
Commented:
To check log file run this command

ESEUTIL /ML E00.log

First try to recover your dirty shutdown with using switch /r if id does fails then you can go for /p for hard recovery but this could be cause of some data lose. So if you have any latest backup try to restore the latest backup and mount it.
Shivkumar SharmaOperations Delivery Manager
Commented:
I agree with aki

First run -  eseuitl /ml "Path of the log file'

The above result will let you know if the log files are ok, if they are ok then do a soft recovery

eseutil /r E00 /l"Path of the log files" /d"Path of the database"  /I /A

If the log files are corrupt then you may add /A option for LLR feature in Exchange 2007
Commented:
Agree with the others here and if you end up needing to run an eseutil /P to repair that database, be sure to run

A. make a copy of the database before you do anything

B. Run eseutil /P  (this can run fast or take some time so be patient

C. if you need to get up and running fast then I would go with the dial tone method as referenced above

D. Run eseutil /D to defrag after  and when that is complete run "isinteg -s servername -fix -test alltests"  to get the database as clean as possible AND you will want to run that command until it reports that it fixed Zero (0) errors.  Usually this has to happen at least twice

E. Mount that database and take an immediate full online backup

F. Create a new database and move the users from the damaged database into the new one and change your backup to protect the new DB.

G. if that old database has the system attendant mailbox you will need to move it as well, here is a link discussing how to http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/846b0d0f-f1bf-4ab0-ade5-60e615b0f6c6

H. When all is well I would dismount the old DB for a few days and if there are no further issues then you can delete that database from Exchange Management System and the DB files on disk as well.

If you are going to look for a third party tool Kroll is a decent product but fairly expensive and there are some really inexpensive tools out there but the quality is not so great when you start to validate the accuracy and completeness of the data.  If you do a search on "Export mailboxes from Exchange 2007 offline database" or similar strings you will see a few options and you can download demo versions that will allow you to see into the database and some can even do a repair for you.   Anyway if you go this direction you could;

1. Copy the database offline so that you have a master copy
2. Make a working copy of that
3. use a 3rd party tool to open the working copy
4. once you can see the data, go to the exchange server and rename the original database file name to something different i.e. if it was Mail.edb change it to OldMail.edb
5. Now go into Exchange Management and mount that database
6. Exchange will tell you that the database files are missing and if you continue you will create a new DB
7. Say yes and a new DB will be created and mail will begin to flow again
8. Users can now connect but the old data will not be there (yet)
9. Use the third party tool to back-fill the missing data on the fly while users work NOTE: Some not all 3rd party tools can do this, others will force you to do the PST shuffle rather then the direct import/merge i.e you have to export the data to PST and then use MS tools to import the PST's
10. Run your backup to get things protected again
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates?
Shivkumar SharmaOperations Delivery Manager

Commented:

Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question. Thank you sir
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question. Thank you sir