Exchange DB corruption? 1

[mspope]

Arc serve 2000 SP4 on Win2k pro, Exchange 5.5 on WinNT4 SP6a

When backing up the Information store, at about 90gigs in, I get the error:
E8602 Failed to read from database. (DBNAME=Information Store, EC=Backup Agent Error -- (69) "Read/Write error in named pipes.".)

The log says:
Total Databases............... 1
Total Skips................... 0
Total Size (Disk)............. 1 KB
Total Size (DB)............... 0 KB
Total Size (Media)............ 90,365.62 MB

"Total Size" tells me I don't have a database backup.

The DBExch.log says:
11/19/02 20:31 MS Exchange Server Message -- A read verification error occurred.
11/19/02 20:31 Backup Agent Error -- (69) "Read/Write error in named pipes."


I think I've got a DB corruption, and I'm just looking for confirmation. Your opinion.

 

[databasebaba]

Apply the patch from the URL given below,

http://support.ca.com/Download/patches/asitnt/QO22840.html

DatabaseBaba

 

[mspope]

Thanks, but that patch is for brick level problems (DBExch2). This was an attempt on a full backup.

We've since determined that we've got a page level Database error and are now working with Microsoft.

 

[speshalyst]

Guess DBbaba got confused...

check if you have any antivirus software running during the backup window..

Set the AV software to backup incoming files only...

you might have to run the ISINTEG on your exchange databases.

check MS support site for detailed info about ISINTEG So it Shall be Written!
So it Shall be Done!!

 

[mspope]

I've got a single 4kb page reporting the wrong checksum. It's in the 1-24 table, meaning it's part of an attachment. I have to run an edbutil repair to remove it. Problem now is disk space......

Used Microsoft articles 314917, 262196, 248406 & others....

 

[fritz4000]

Whenever I have seen a named pipe problem during the database level of backup, the cause has been corruption. The only tru way to test is the exchange utilities, which normally involves bringing Exchange offline. If you are not familiar with the utilities, I would contact MS or their website to check out how to use them. I understand they are pretty powerful and if the find corruption they can just wipe out whatever the cause is.