Have you verified if it's a hardware issue? Did you run your manufacturers diagnostic software on your controller? Have you tried different tapes? Do you see any hardware events in your system log? Have you tried upgrading controller drivers firmware? You want to try to rule out hardware issues before running utilities on your Exchange DB. ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Amit Kapoor Sent: Tuesday, April 04, 2006 5:07 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: Syntax for ISINTEG. Importance: High Hi I need to run ISINTEG on private database i.e priv1.edb. Because when I perform backup using NTBackup it gives me error and just copies 20 MB of data to the backup file. There are no such errors on the public database store. Following is the error message that I am getting on private database store. Information Store (3028) First Storage Group: The database page read from the file "D:\exchsrvr\mdbdata\priv1.edb" at offset 20656128 (0x00000000013b3000) for 4096 (0x00001000) bytes failed verification due to a page number mismatch. The expected page number was 5042 (0x000013b2) and the actual page number was 1929384882 (0x730013b2). 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. Please Help. ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of ChongJa@xxxxxxxxxxxxxxxx Sent: Monday, April 03, 2006 7:45 PM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: Syntax for ISINTEG. Are you having some issues with your public database store that you're wishing to perform isinteg? 1. Make a backup of your public database store using your backup software. To be extra safe, I would also copy that database file off to another server. 2. To run isinteg, dismount your public folder store in ESM. Open command prompt, go to where exchange was installed, your program files\exchsrvr\bin directory. Type isinteg -s servername -fix -test alltests. At the end of an Isinteg fix run, you will likely see hundreds to thousands of warnings. The thing you need to worry about is not warnings, but errors. You need to run isinteg until there are zero errors reported. 3. It's always recommended to run defrag after you perform isinteg. Go to your command prompt again, into your exchsrvr\bin directory. Type eseutil /d "E:\EXCHSRVR\priv1.edb" (Your path of your db) ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Amit Kapoor Sent: Monday, April 03, 2006 8:15 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Syntax for ISINTEG. Importance: High Hi All, I want to run ISINTEG on priv1.edb database. Will it have any impact on the Public Database store. I was suggested this by few List members, but I have problem in taking backup of Exchange 2003 server. Do I take offline backup of the database, if in case anything went wrong, then I can restore the database from offline backup. (offline Backup means folder backup) My question is : 1) Will Offline Backup be useful. 2) Syntax for executing ISINTEG on private edb database. 3) Do I need to run eseutil after running ISINTEG tool. Regards Amit <http://351879.sigclick.mailinfo.com/sigclick/02000909/070B4F0E/06490A71 581023.jpg>