Re: Corrupt Mailbox Store

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mark (anonymous_at_discussions.microsoft.com)
Date: 04/19/04


Date: Sun, 18 Apr 2004 18:00:01 -0700

Thanks for the help! This seems to have worked. I only
have one question. After recreating a new store and using
exmerge to copy all of the mailboxes back in the number of
logfiles for exchange grew probably 100 times what they
were. Before I probably only had 80 or so logfiles and
now I have over 800. This concerns me since each logfile
is 5 MB. Did I do something wrong or is there a way to
get rid of all of these log files? Any help would be
appreciated.

Thanks,

Mark
>-----Original Message-----
>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: One database not backing up
    ... No matter where your log files are you still need to get a working backup to ... If you have some breathing space then investigate further why you are not ... You could run eseutil /k against the suspect store just to check all the ...
    (microsoft.public.exchange.admin)
  • Re: Log files in ExchsrvrMDBDATA
    ... Now you found out why you must not delete the transaction log files. ... will be deleted when you run an online backup of the information store. ... database with an eseutil /d. ... Then mount the store. ...
    (microsoft.public.exchange2000.win2000)
  • Re: corrupt backup
    ... But in fact, a store ... commits the log files to Exchange and deletes them. ... destination folder from the previous backups so the log files from the ... the backup folder it sees all of the log files and throws the error "An ...
    (microsoft.public.exchange.misc)
  • Re: corrupt backup
    ... But in fact, a store that has shut down cleanly doesn't need any transaction logs, their value is in restoring a previous store in case the current store fails so you don't lose data. ... > commits the log files to Exchange and deletes them. ... > current backup reside in the same destination folder as the old log> files. ...
    (microsoft.public.exchange.misc)
  • Re: Log files in MDBDATA folder
    ... >I am using Veritas Backup Exec to backup my exchange ... >am only backing up the Exchange Mailboxes and not the ... Information Store, coz ... >> lazily written from the log files into the database. ...
    (microsoft.public.exchange.admin)