Dave
Thu Mar 03 17:25:43 CST 2005
Chris - this sounds like the problem I was having. Exchange seemed to be
working normally, but backups were failing with at least some of the errors
you posted. Everything in this scenario points to hardware, but I had what
I considered were some pretty good reasons for thinking otherwise -
relatively new server, no other indication of hardware problems including
having run all the Dell diagnostics, old database updated several times, and
the problem occurred immediately upon install of Exchange 2003 SP1.
When I called PSS, I could not really convince the tech that my problem was
not hardware. However, he thought I should try to repair the databases
because there was no reason to think my recent backups were any better than
the production databases.
I still recommend calling PSS. But at the least, read these 2 KBs:
http://support.microsoft.com/default.aspx?scid=kb;en-us;327334
http://support.microsoft.com/default.aspx?scid=kb;en-us;810411
If you want to attempt the repair process, here's how, remembering that if
your problem really is hardware, this will be a temporary fix at best:
How to recover the information store on Exchange 2000 in a single site
http://support.microsoft.com/default.aspx?scid=kb;en-us;313184
I'm not sure how seriously to take the warnings about data loss from this
procedure. I know that it tosses any unreadable database pages, but I don't
think the unreadable pages are likely to be worth much anyway. Four other
things: it may not be clear that the free space needed to run eseutil needs
to be on the drive you're running it from. So, if eseutil is on C and the
databases are on D, the free space needs to be on C, not D as you may
logically assume. If that's a problem, you can copy the \bin directory to D
or wherever you have enough space. Also if it's not clear in the KB, you
want to copy the databases, then run the utilities against that copy. Leave
the original databases somewhere untouched so you have them to fall back on.
And, there's something in the KB that indicates that you repeat certain
steps if you get errors more than once - I had to do all that stuff twice,
so don't worry if you run into the same thing. And lastly, you can expect
this to take a while. My databases are 5-6 gb, and I'd guess it took 3
hours, but it depends on hardware too.
Good luck, and let me know how you make out.
"Chris Guimbellot" <cguimbellot@FORGETSPAM.hifranchise.com> wrote in message
news:%23t6667DIFHA.4076@TK2MSFTNGP10.phx.gbl...
> Dave,
>
>
>
> Thanks for the response. I checked the logs between the time the backup of
> Exchange started and ended, I received the following messages:
>
>
>
> Type: Error
>
> Course: ESE
>
> Category: Logging/Recovery
>
> EventID: 474
>
> Description:
>
> Information Store (3464) The database page read from the file
> "D:\Exchange\priv1.edb" at offset 3688574976 (0x00000000dbdb3000) for 4096
> (0x00001000) bytes failed verification due to a page checksum mismatch.
> The expected checksum was 3129815682 (0xba8d3282) and the actual checksum
> was 4253462929 (0xfd86b191). The read operation will fail with error -1018
> (0xfffffc06). If this condition persists then please restore the database
> from a previous backup.
>
>
>
> (I received that error many times)
>
>
>
> Type: Error
>
> Course: ESE
>
> Category: Logging/Recovery
>
> EventID: 217
>
> Description:
>
> Information Store (3464) d03bde12-613c-4c4a-abde-bb7b068172bd: Error
> (-1018) during backup of a database (file D:\Exchange\priv1.edb). The
> database will be unable to restore.
>
>
>
> Type: Information
>
> Course: ESE
>
> Category: Logging/Recovery
>
> EventID: 222
>
> Description:
>
> Information Store (3464) d03bde12-613c-4c4a-abde-bb7b068172bd: Ending the
> backup of the file D:\Exchange\priv1.edb. Not all data in the file has
> been read (read 3688562688 bytes out of 4921372672 bytes).
>
>
>
> Type: Error
>
> Course: NTBackup
>
> Category: None
>
> EventID: 8012
>
> Description:
>
> The 'Microsoft Information Store' returned 'Error returned from an ESE
> function call (d).
>
> ' from a call to 'HrESEBackupRead()' additional data '-'
>
>
>
> (I received that error twice)
>
>
>
> Type: Error
>
> Course: NTBackup
>
> Category: None
>
> EventID: 8012
>
> Description:
>
> The 'Microsoft Information Store' returned 'Error returned from an ESE
> function call (d).
>
> ' from a call to 'HrESEBackupClose()' additional data '-'
>
>
>
> There is one other thing that is probably relevant. I think its possible
> that folder where I moved the Exchange databases to may have been scanned
> last night accidentally. I know that's not supposed to happen, but I
> believe it did. I am not sure if that could be the answer.
>
>
>
> I have no idea what to do, the nightly backup starts in five hours and I
> am not sure if I should allow it to run tonight.
>
>
>
> I appreciate the help.
>
>
>
> Chris
>
>
> "Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in
> message news:uU4dWxDIFHA.2984@TK2MSFTNGP15.phx.gbl...
>> Chris - can you please post the exact error you're seeing, with the error
>> codes etc?
>>
>> Our firm has a huge amount of critical data in Exchange, so I would
>> always call PSS if I thought that data was at risk. I had a similar
>> situation to what you describe earlier this year. If your error is the
>> same one I had, I can let you know what fixed it.
>>
>>
>> "Chris Guimbellot" <cguimbellot@FORGETSPAM.hifranchise.com> wrote in
>> message news:OJ0z5N$HFHA.980@TK2MSFTNGP12.phx.gbl...
>>> Hello,
>>>
>>> SBS2000. Last night, I moved my EDB and STM files for both my Mailbox
>>> Store and Public Store to another drive on my server by following the
>>> directions in the following articles (they all say essentially the same
>>> thing):
>>>
>>>
http://www.msexchange.org/pages/article_p.asp?id=535
>>>
http://support.microsoft.com/?kbid=270693
>>>
http://www.smallbizserver.net/Default.aspx?tabid=76
>>>
>>> I did not move the transaction logs because the MSExchange.org article
>>> eluded that they should not be on the same drive. That said, I left the
>>> transaction log location alone and only moved the databases.
>>>
>>> Anyway, the move went well. All users can get into their mailboxes
>>> without a problem, but when I checked the log from last night's backup,
>>> I received the following message:
>>>
>>> WARNING: Portions of "\Mailbox Store (HI-SERVER)" cannot be read. The
>>> backed up data is corrupt or incomplete.
>>> This file will not restore correctly.
>>>
>>> This makes me very nervous. Does anyone have any idea of what's wrong
>>> here? Any help would be most appreciated. Thanks,
>>>
>>> Chris
>>>
>>
>>
>
>