Improve company productivity with a Business Account.Sign Up

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

Can't run Exchange logs

My Exchange backup failed because of a disk error. When I check my Exchange server one of the disks in the RAID 5 array had failed. I replaced the drive and as the array was rebuilding a second drive failed. This caused a complete parity error and the server blue screened. I restarted into the array utility and rebuilt the array, but when the server rebooted the Exchange stores would not mount because of a check file inconsistency. I assume this is because the array failure interrupted some writes. I had a good backup from 6/2 but it would not restore over the old backup because of a file error.

I could NOT allow the email server to remain down any longer because it is business critical. About 70% of our business is transacted through email. So I moved the edb and stm files and brought the stores up so new business could be conducted. I then restored the 6/2 backups into a recovery storage group and merged those mailboxes with the online boxes.

I now have gap in email from 6/2 to 6/18. I have tried eseutil /p and /r and /cc to write the logs from 6/2 through 6/18 with no luck. I have also used isinteg to and still no good.

Does anyone have a suggestion to run the logs from 6/2 through 6/18 into my stores?
0
mathewmc
Asked:
mathewmc
  • 3
  • 3
1 Solution
 
consultkhanCommented:
Yes you could do that only IF all the logs are in sequence available and in good shape including res1.log and res2.log .
check the signatures of database files agaist the log files and verify that you could use them.

Good Luck!
0
 
mathewmcAuthor Commented:
I am not sure what you mean by 'do that'. How are you suggesting I run the logs?
0
 
consultkhanCommented:
This is what i was suggesting in detail:-
1.Restore the databases to an alternate server in a test environemnt (with a seperate Active directory )
2.DO not select "mount the databases after restore" option
3.the log file from the tapes would go to a temporary location (environment)
4.copy the logs from 6/2 to 6/18 to the production location (on the same server)
5.run eseutil/ml on all the log files to veify log are ok
6.rename the last log from the production ares to E00.LOG
now run the eseutil /cc "database area" on the restore environment.
7.watch for the application logs for the event

thanks.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
mathewmcAuthor Commented:
That was what I tried first. It didn't work. I beleive that when the back up failed it had partially commited the logs. Eseutil /ml shows everything OK and Eseutil /mh shows there are no logs needing to be committted. Yet we are still missing the emails from 6/2 to 6/18.
0
 
consultkhanCommented:
Even if the log file required shows 0-0 you should be able to do a roll-forward I mean play the log files to put them into the database.
Log file required parameter however, will not moun the datbase if that particular log file is missing ,since its 0-0 you can mount the database and you can roll forward if you wish.
this article talks about the same situation.
have a look
http://technet.microsoft.com/en-us/library/aa996238(EXCHG.65).aspx
thanks.
0
 
mathewmcAuthor Commented:
There were no damaged logs, no time mismatches and no missing logs. They just won't commit. I finally used a tool called Stellar Pheonix Exchange EDB Recovery. I recovered 85% of the emails. We'll just have to live with that. Since you were the only who helped you get all the points. Thank you.
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

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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