Hello,
SBS2K. On March 3rd, I submitted a post about possible corruption in my
Exchange database. Basically, I moved the database to a new SCSI drive I
purchased and install. The move went well and the users had no problems with
their mailboxes, but when I checked the backup log after the first backup, I
noticed the following error:
WARNING: Portions of "\Mailbox Store (HI-SERVER)" cannot be read. The
backed up data is corrupt or incomplete.
This file will not restore correctly.
After some research and some outside help (thanks Dave), I discovered 474
errors. Also, ntbackup will not allow me to restore the database from the
backup. When you look on support for error 474, you come up with the
following articles:
XADM: Event ID 474 Error Indicates a Hardware Failure
http://support.microsoft.com/default.aspx?scid=kb;en-us;327334
XADM: Extensible Storage Engine Event IDs 474 and 477 Are Logged When You
Try to Back Up the Information Store Database
http://support.microsoft.com/default.aspx?scid=kb;en-us;810411
Both of these articles eluded to a hardware problem with the drive. I called
tech support for Maxtor and was told that one possibility is that I needed a
twisted (if that is the correct term) cable. That said, I am going to
purchase the cable.
Until I can get the cable in and installed, I have moved the Exchange back
to the original drive it was on. It is still corrupted according to the
backup log, and I continue to log 474 errors. After I moved the database
back to the original drive, I tried the suggestions in the following article
(thanks again Dave):
How to recover the information store on Exchange 2000 in a single site
http://support.microsoft.com/default.aspx?scid=kb;en-us;313184
The article recommends running the following command and checking the result
of the line labeled "State":
C:\Program Files\exchsrvr\BIN>eseutil /mh "drive:\Program
Files\exchsrvr\MDBDATA\priv1.edb"
When I ran the command, I saved the result to a text file. Below is the
content of the text file:
Microsoft(R) Exchange Server(TM) Database Utilities
Version 6.0
Copyright (C) Microsoft Corporation 1991-2000. All Rights Reserved.
Initiating FILE DUMP mode...
Database: c:\program files\exchsrvr\mdbdata\priv1.edb
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,9
Engine ulVersion: 0x620,9
Created ulVersion: 0x620,9
DB Signature: Create time:04/01/2002 17:11:13 Rand:4481249 Computer:
cbDbPage: 4096
dbtime: 101277021 (0-101277021)
State: Clean Shutdown
Log Required: 0-0
Streaming File: Yes
Shadowed: Yes
Last Objid: 103559
Scrub Dbtime: 0 (0-0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 0
Repair Date: 00/00/1900 00:00:00
Last Consistent: (0x1D0F,1237,49) 03/08/2005 07:06:17
Last Attach: (0x1CF9,B58,34) 03/04/2005 19:37:49
Last Detach: (0x1D0F,1237,49) 03/08/2005 07:06:17
Dbid: 1
Log Signature: Create time:04/01/2002 17:11:09 Rand:4508100 Computer:
OS Version: (5.0.2195 SP 4)
Previous Full Backup:
Log Gen: 7382-7382 (0x1cd6-0x1cd6)
Mark: (0x1CD6,17CA,141)
Mark: 03/02/2005 01:31:14
Current Incremental Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Full Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current snapshot backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
cpgUpgrade55Format: 0
cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0
Operation completed successfully in 1.92 seconds.
When I was reading the article, I was looking for the "State" line to say
something to the effect of 'consistent' because that's what the article
refers to. When I received 'State: Clean Shutdown', I didn't know what that
meant, but I know that it doesn't sound corrupt to me.
That said, where do I go from here? Should I begin following the other steps
in the article? I haven't because I am not sure if the results from the
first command tell me to not run any of the recovery options. The users can
still access their mailboxes and nothing appears to be wrong at their end,
but I cannot back up the databases and that is not a good thing. Also to
note, if I go to the folder that houses the priv1.ebd file, I see log files
which, according to their modified date, go all the way back to the day I
originally installed the new disk and moved the database starting all this
mess. I am not sure if that is relevant, but I figured I would mention it.
If nothing works, I may have to call PSS (another result of Dave's help)
which is not a problem, but I figure there may be a way around this that
someone would know if I provided the correct information and enough of it. I
appreciate any help someone can give on this. Thanks again,
Chris