I was called in to take a look at a down exchange server (2003, part of a small sbs 2003 installation).
There is a small number of users (<10) with a small exchange database (<4GB).
Today, the server went offline, froze, and hard to be hard reset. It came up fine, except the database for exchange would not mount.
I looked at the logs and before the freeze I see this:
Information Store (2240) First Storage Group: A request to write to the file "D:\exchange\Logs\E00tmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes succeeded, but took an abnormally long time (95 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
A few minutes later:
Information Store (2872) First Storage Group: Corruption was detected during soft recovery in logfile D:\exchange\Logs\E00.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 517 (0x00000205). This logfile has been damaged and is unusable.
Then the store went down and this even occurred:
Information Store (2872) First Storage Group: Database recovery/restore failed with unexpected error -501.
Error Log file is corrupt starting Storage Group /DC=local/DC=domain/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=First Organization/CN=Administrative Groups/CN=first administrative group/CN=Servers/CN=SERVER/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.
They have no decent backup and there are a LOT of log files that have not been rolled into the database.
I just want to verify the order of steps I should be taking here. I have made a manual backup of the edb files and log files. Could someone list the steps I should take that will lead to the least amount of data loss?