• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 760
  • Last Modified:

MS Exchange missing/corrupt log files

Our Exchange Server shut down on Monday night becasue it ran out of space on the Hard Disk Drives. It was a clean Shutdown and we backed it up.

We managed to restore the database yesterday after making more space available  (36 hours later). Email then worked for about 18 hours until it crashed today.

We ran the Microsoft Exchange Troubleshooting Assistant v1.1 which gave us the following

result:
Database status is Dirty Shutdown

Details:
There are missing or mismatched log files.
Missing or mismatched log files: E0000030FB6.log  E0000030FC1.log (Ive converted these from hex to decimal and it equates to 11 log files in total).

Solution:
Problems with the log files listed above must be resolved before this database can be recovered.

How can we get Exchange back up and running? We are thinking of restoring the clean shutdown backup from monday night and then trying to replay the available log files generated during the 18 hours that Exchange was running between yesterday and this morning.
0
GerryPeak
Asked:
GerryPeak
  • 4
  • 3
1 Solution
 
tompi68Commented:
if you restore a clean shutdown db you can not replay any further log files. (because the db is in clean shutdown!). You can only restore the clean shutdown db , or you run eseutil /p on the dirty shutdown db. If you do that, run eseutil /p afterwards. After you ran eseutil /p you have to remove all the log files in the dir to mount the db.
0
 
tompi68Commented:
PS: You can try to import the LOG Files with eseutil /r
http://technet.microsoft.com/de-de/library/bb123479.aspx

It´s worth a try
0
 
GerryPeakAuthor Commented:
The problem is the mismatched or missing log files. We have not run esutil /p yet and perhaps we should be looking at Cross-Matching Exchange Databases and Log Files:

http://technet.microsoft.com/en-us/library/aa996238(EXCHG.65).aspx
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
tompi68Commented:
This article only describes how to identify the correct log files . But if log files are missing? I do not know any technique to restore a db with missing log files. Sorry
0
 
GerryPeakAuthor Commented:
>>
PS: You can try to import the LOG Files with eseutil /r
http://technet.microsoft.com/de-de/library/bb123479.aspx
<<

I;ve loooked at that artice and it isn't clear how to IMPORT log files into a clean shut down?
0
 
abhaighCommented:
eseutil /p will sort the problem out and let you mount the store again
0
 
GerryPeakAuthor Commented:
We were unable to replay the log files on the clean shut down exchange database
0
 
GerryPeakAuthor Commented:
No solution found
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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