Unusual error in database
From: Aaron Wolski (anonymous_at_discussions.microsoft.com)
Date: 08/22/04
- Next message: anonymous_at_discussions.microsoft.com: "Re: The mailbox objects that won't die."
- Previous message: Lanwench [MVP - Exchange]: "Re: MX - What IP should this point to?"
- Next in thread: Andy David - Exchange MVP: "Re: Unusual error in database"
- Reply: Andy David - Exchange MVP: "Re: Unusual error in database"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 22 Aug 2004 12:06:30 -0700
I am currently attempting to fix a corrupted exchange
server database for a client, that resulted from a power
failure. After exhausting all other options from the
disaster recovery document, I tried to perform a hard
recovery of the private store.
The process appeared to make steady progress until about
~72% through the repair database table section. Here, it
sat, for over an hour until I cancelled. A backup was
available, albeit dated (don't ask), which was restored in
place. The backup would not mount as well, so I proceeded
with a hard recovery of it, hoping that the damage would
be minimal. This time it hit ~78% before all progress
seemed to stop.
This seemed like too great a coincidence to me that,
taking growth of the database into consideration, the
recovery process was stalling in the same spot. Could
there be something fundamentally wrong with the private
store that prevents recovery while it still allowed normal
operation before the failure?
I did make copies of the data immediately after the
failure and after restore from the backup. The next step
may have to be tech support.
- Next message: anonymous_at_discussions.microsoft.com: "Re: The mailbox objects that won't die."
- Previous message: Lanwench [MVP - Exchange]: "Re: MX - What IP should this point to?"
- Next in thread: Andy David - Exchange MVP: "Re: Unusual error in database"
- Reply: Andy David - Exchange MVP: "Re: Unusual error in database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|