Repeat after Andy. Hardware, hardware, hardware. I spent 3+ months with a server trying to figure out why we kept getting database corruption errors. We even had Compaq (this was a while ago) engineering onsite to look at the server. After all that time they finally issued an engineering alert on a specific model built between a certain date that the motherboard needed replacing. It would only cause issues for AD or Exchange databases. Everything else would work fine. It took the Compaq engineers 3 months in their lab to figure out the hardware issue. You won't be able to tell just because the server isn't throwing errors.
If you purchased a white box server, you'll never figure out where the problem is. The big manufactures test their hardware combinations pretty well, but with the white box servers can be anything. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bryce Stenberg Sent: Sunday, February 19, 2006 10:47 PM To: Exchange Discussions Subject: RE: Database corruption problems - how to run isinteg from batch file? Hi Andy, >From what I can tell this new hardware seems to be working fine - it is a stock standard intel dual-processor server board with latest bios in an intel certified case with several harddrives plugged into motherboard. I know the old hardware was probably cause of previous issues due to being woefully underpowered. However, I will take another look at the hardware and see what I can find. NTbackup runs nightly for Exchange and that is not reporting any integrity errors. Regarding the 'JET_errBadPageLink' - can you tell me is that a physical error, not a logical error? The reason I started running the defrag weekly was due to recommendation from Symantec when installed their LiveState Recovery product (http://service1.symantec.com/SUPPORT/powerquest.nsf/docid/2005091309295062) - it recommended: "We recommended that you regularly perform integrity checks on the database by running the following commands: Eseutil /mh >C:\header.txt Performs a header dump and pipes to a file Eseutil /g >C:\integrity.txt Performs an integrity check and pipes to a file Eseutil /k >C:\checksum.txt Creates a checksum You should defragment the database frequently." I'll take your recommendation and stop defrag for now. I will also uninstall LiveState Recovery for a month and see if that is causing the problems (although there documentation in above link primarily refers to corruption of the snapshot image being taken for backup, not the running database). I use to think Exchange was great - I hope I can get there again. Thanks for your help, Regards, Bryce Stenberg. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
