We help IT Professionals succeed at work.

Recovering Exchange database in SBS2008

FMPC
FMPC asked
on
Hi,

I have a corrupt Exchagne Mail Store on my hands (SBS2008). It works as far as I can see but it fails integrity check.
I have a backup to the date when the store was OK.
All computers on the LAN use Cached mode for Outlooks.

What would be the best way forward to recouer the database and to bring it up to speed with workstations?
Comment
Watch Question

Distinguished Expert 2018
Commented:
I'd start with running eseutil against the database. May save you the hassle of even messing with a restore from your backup.
http://technet.microsoft.com/en-us/library/aa998249(EXCHG.80).aspx
 

Author

Commented:
I did run the ESEUTIL /G and it confirms a corruption.
Running EEUTIL /R E00 lasts a second and doesn't result in a good database
The store mounts by the exchange.

Author

Commented:
If I re-write corrupt database with a copy of good one, would cached mode from Outlooks push the missing data in automatically?

Author

Commented:
I would rather avoid ESEUTIL /P if I can help it.
I have a mailstore.edb which is fine and clean closed. Then I have 5 days backups which include now corrupt mailstore.edb and lots of .log files. How do I replay those later .log files into the old clean database?
Distinguished Expert 2018
Commented:
If you've been performing backups then there is no gaurantee that you have enough logs to get an old backup back to a consistent state. Part of the VSS process is pruning logs.  I'd make a copy of the existing store, run the repair and see what is missing. You can mount the copy of the existing store (since it does seem to mount) into a recovery group and move missing data as necessary.
In many cases, if a database mounts, a repair won't lose any data, but it is a corrupt index or other meta-data type corruption that is causing the errors. ...but as always, that is an "in many cases" scenario and backups and contingency plans are still important.

Author

Commented:
cgaliher,

Thank you. Is there a recommendation to configure SBS 2008 to keep logs separately and for a longer time?
Distinguished Expert 2018
Commented:
No. Usually if a corruption occurs, you'll know about it right away (things go wrong) and if it is a subtle issue, it could go unnoticed for longer than you configure your retention policies no matter how long out you configure them for. So this really is just an edge case and there is nothing SBS specific about it.

Author

Commented:
It is somewhat hard to beleive that exchange database recovery is limited to just restoring an old copy. I may be wrong but isn't there a more advanced method of getting data back from all available sources?