Question : Exchange 2003 Server will not backup Corrupt Database

Hi,

I have a single Exchange 2003 Server.

The Server hung over the weekend and when i came to do a full Exchange backup last night i get the following event log:

Event Type:      Error
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      478
Date:            08/01/2008
Time:            14:22:41
User:            N/A
Computer:      TEMPMAIL2K3
Description:
Information Store (2812) The streaming page read from the file "I:\Exchsrvr\Mdbdata\priv1.stm" at offset 2367279104 (0x000000008d19d000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch.  The expected checksum was 479293938 (0x000000001c9171f2) and the actual checksum was 3165573775 (0x00000000bcaed28f).  The read operation will fail with error -613 (0xfffffd9b).  If this condition persists then please restore the database from a previous backup.

For more information, click http://www.microsoft.com/contentredirect.asp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I have tried to do an offline defrag and even tried to verify it by using the command eseutil /g
Every time i do this is hangs the server and i have to do a hard reset.

Can anybody advice on this problem please?

I am using Veritas Backup 11D

An offline defrag would probably resolve this but i can't do one due to is always hanging the server at a point.   Exchnage is fuctioning but without a backup i fear,

Answer : Exchange 2003 Server will not backup Corrupt Database

You can archive the logs off, but you'll need them to fully recover.  You may find that this gets pretty complicated if you aren't able to put them back where they were.  I'd use BE to back them up if you can.  If you use an incremental backup, it'll remove them from the Exchange folder.  Feel free to copy them first.

Your primary option is always the recover from tape and use the logs to go forward.  I'd phone Microsoft Product Support (or a Veritas engineer) if you are still struggling to get it to work.  MS support can be expensive, but I've had good engineers on the phone for four hours helping me to get things sorted in the past.  They're often worth the money!