asked on

Exchange 2003 database is corrupt. Cannot backup.

Hello.

My current Exchange 2003 database is corrupt and backup exec and ntbackup will not successfully backup the database. When I went to perform a restore, Backup Exec stated that the backups were corrupt. The last good backup was over a month ago.

Event viewer reports Event ID 478.
The expected checksum was 3201341912 (0x00000000bed099d8) and the actual checksum was 2309737967 (0x0000000089abcdef). The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup.

I am running Exchange 2003 Standard. Is there another alternative to restoring the month old database and then trying to import in the new data? I have never ran into this issue and would appreciate any assistance.

Can I perhaps run exmerge on the "LIVE" database and somehow import all of the database into a new database and switch it out with the current corrupt database?

SOLUTION

Britt Thompson

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

jesusrulesme

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Britt Thompson

Actually, ISINTEG FIX is probably what you'll need to do.

jesusrulesme

Wow, renazonse...looks like we're on the same page. :-)

xtmsports

ASKER

Thanks renazonse and jesusrulesme.

I will try these tonight and update you.

Britt Thompson

Yeah...don't you hate that. For once I typed faster than someone else.

xtmsports

ASKER

Just another piece of information since you both recommended using the eseutil.

I performed an offline defrag about a month ago and it failed with the following error:

checksum error in SLV file during backup

Operation terminated with error -613

(JET_errSLVReadVerifyFailure, Checksum error in SLV file during backup)

Britt Thompson

Yeah...same thing. Need to run the repair.

ASKER CERTIFIED SOLUTION

gauravbhandari

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

gauravbhandari

Additional Information: RSG can only be used for Mailbox Store & not for Public Folder Store.

xtmsports

ASKER

I talked to MIcrosoft and the recommended that I unmount the database and then moved/renamed the folder containing the transaction logs. Then mount the database and it will recreate the transaction log folder. Then run NTbackukp; which I did do and not luck.

Second suggestion was to run isinteg -s (server) -fix -test alltests

The first time I ran it, it had 53 fixes, so I ran it a second until I received ALL zeroes. Then I ran NTbackup and still no luck.

Now Microsoft is saying its probably hardware related to my hard disk. It sounds like Microsoft is blowing smoke now.

Any other suggestions would be appreciated.

Thanks.

xtmsports

ASKER

Hi guy,

Microsoft was blowing smoke and I called them on it regarding a hardware issue. I ran a backup of the public store with no issues on the same hard drive. So that eliminated their guess of a hardware issue.

I ended up doing a database repair with the eseutil /p "D:\Exchsrvr\Mailbox Store (SERVER).edb"

Then ran a defrag and isinteg.

Thanks for all your help!