Re: Corrupt Mailbox Store

From: Charlotte Zinck [MSFT] (czinck_at_online.microsoft.com)
Date: 04/16/04


Date: Fri, 16 Apr 2004 17:57:36 -0500

Mark,

Since your backups are failing and you have tested your database and it
comes back with corruption detected I would recommend that you act now.

Since you can still mount your mailbox (it could dismount at any time) then
you could create a new store and move the mailboxes to it or use Exmerge to
export the data out to PST files and then import the PST files back into a
new store. Either of these steps will eliminate the corruption.

If the database does not mount then you will have to resort to restoring the
last known good backup and reading through the log files that are still on
the harddrive.
Here is the article on doing the restore and reading through the existing
log files:
821511 How to Replay Log Files That Have Been Generated Since the Last Full
http://support.microsoft.com/?id=821511

Finally, you will want to determine why the database has become corrupt.
You will want to use the backup log as well as the application log to
determine if this is a hardware problem. If this is an issue with hardware
then you will want to replace the defective hardware or move the databases
to new hardware or the corruption may creep up again.
Here is an article that talks about hardware problems:
314917 XADM: Understanding and Analyzing -1018, -1019, and -1022 Exchange
http://support.microsoft.com/?id=314917

Hope this helps,
Charlotte Zinck [MSFT]
Microsoft Exchange Support

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark" <anonymous@discussions.microsoft.com> wrote in message
news:1de9201c423d2$ff4e91a0$a101280a@phx.gbl...
> Help! I use veritas backup exec to do daily full backups
> on my mail server. The past week the backup job has been
> failing when it is verifying. I have been doing a bunch
> of troubleshooting and have determined that the database
> is corrupted. I ran the eseutil exchange utility in
> integrity mode and it came back with "database is
> corrupted" I am having no email problems and have no
> problems mounting and dismounting the store when
> needed...It is just the verify on the backups that fail.
> What should I do?? Do I need to create a new store and
> export all of my mailboxes to that new store? What is
> the best way to fix this problem? Any help would be
> greatly appreciated.



Relevant Pages

  • RE: Information Store Corrupted
    ... depend on the kind of storage you are using. ... If the corruption is a database structure page you will not ... The backup by definition doesn't include the corrupted items. ... Category: Database Page Cache ...
    (microsoft.public.exchange.admin)
  • Re: Copying Tables
    ... copy of my tables in another database on a different machine. ... Should I use transferdatabase to get the info into the backup ... "Corruption will only manifest itesl ... want a transaction by tranaction copy of my database so that I ...
    (microsoft.public.access.formscoding)
  • Re: Copying Tables
    ... copy of my tables in another database on a different machine. ... Should I use transferdatabase to get the info into the backup ... "Corruption will only manifest itesl ... want a transaction by tranaction copy of my database so that I ...
    (microsoft.public.access.formscoding)
  • Re: Copying Tables
    ... of my tables in another database on a different machine. ... Should I use transferdatabase to get the info into the backup ... "Corruption will only manifest itesl ... want a transaction by tranaction copy of my database so that I ...
    (microsoft.public.access.formscoding)
  • Re: Exchange database keeps getting corrupted
    ... You need to take the comment about hardware seriously. ... >> I haven't heard of a user mailbox corrupting Exchange. ... >>> is that the database keeps getting corrupted. ... >>> There are a few other ESE errors that generally say that a corruption ...
    (microsoft.public.windows.server.sbs)