Re: Error in Exchange
- From: "Todd Booher" <tbooher@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 Oct 2006 14:15:46 -0700
If your Sept 8th backup is good I would restore from that and then do a repair
offline on your corrupt database and export out everything from Sept 8th forward
using exmerge.
You really should try to find the hardware issue first as it will most likely corrupt
your database again. I would also open a case with PSS as they can assist you better
than the newsgroups.
Todd
"Gureey" <Gureey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:629DC87A-BFEE-4936-ADBF-A06A48720646@xxxxxxxxxxxxxxxx
Thanks Todd
If this is then, I have one more question to you,
Database corruption error logged on Sept 14 on our server and I take a full
backup on Sept 8. Database corruption is gone after daily maintenance is run.
On Oct 6 I again take a full backup of exchange and as you know, all
transaction logs are saved in that backup. When DB corruption error came,
circular logging is enable on our server, I disable it.
As you mention, I restore the Backup that I take on Oct 6 and replay the log
files according to the documentation. After that these error’s came in when
maintenance run.
Tell what is the best option right now. Coz I don’t have transaction logs in
full backup on Sept 8. do I restore again from last full backup (“what about
transaction logs after Sept 8)
Regards
Guri
"Todd Booher" wrote:
It's an Exchange database corruption issue most likely caused by faulty
hardware. At this
point your best bet is to restore from backup (before those events began)
and then it
will replay your logs (assuming a full backup has not been able to complete
since there
errors). If a backup is not available you will need to do a repair on the
existing database
but you will definitely see some data loss at that point. I would
concentrate on finding
the faulty hardware before that since the problem will most likely come
back.
http://support.microsoft.com/kb/810411/en-us
http://support.microsoft.com/kb/812531/en-us
http://support.microsoft.com/kb/867626/en-us
Todd
"Gureey" <Gureey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:73D17AC0-F97A-418D-A195-4EEDA8B40FDA@xxxxxxxxxxxxxxxx
> Hello Friends,
> This error messages are logged in Events, when Maintanace is run on
> exchange
> database.
> Information Store First Storage Group: The database page read from the
> file
> "D:\Exchsrvr\MDBDATA\priv1.edb" at offset 4239945728 > (0x00000000fcb87000)
> (database page 1035142 (0xFCB86)) for 4096 (0x00001000) bytes failed
> verification due to a page checksum mismatch. The expected checksum > was
> 4445902399428239 (0x000fcb865139568f) and the actual checksum was
> 4445902533645967 (0x000fcb865939568f). The read operation will fail > with
> error -1018 (0xfffffc06). If this condition persists then please > restore
> the
> database from a previous backup. This problem is likely due to faulty
> hardware. Please contact your hardware vendor for further assistance
> diagnosing the problem.
>
> Information Store First Storage Group: Online defragmentation of > database
> 'D:\Exchsrvr\MDBDATA\priv1.edb' terminated prematurely after > encountering
> unexpected error -1018. The next time online defragmentation is started > on
> this database, it will resume from the point of interruption.
>
> Is this a hardware problem or exchange problem, How can i fix these
> errors.
>
> Regards
> Guri
.
- Follow-Ups:
- Re: Error in Exchange
- From: Gureey
- Re: Error in Exchange
- References:
- Re: Error in Exchange
- From: Todd Booher
- Re: Error in Exchange
- From: Gureey
- Re: Error in Exchange
- Prev by Date: Re: Some email not being delivered
- Next by Date: Re: RPC over HTTP "Exchange Server is unavailable"
- Previous by thread: Re: Error in Exchange
- Next by thread: Re: Error in Exchange
- Index(es):
Relevant Pages
|
Loading