Defragging an exchange 2003 database

thecomputerplace
thecomputerplace used Ask the Experts™
on
Hi experts, i am trying to defrag an exchange 2003 database.
It's running Windows 2003 Server Standard sp2 with exchange sp2 also.  The server has 4GB Ram and a Xeon 3.06Ghz processor and about 120% free space in relation to the exchange db size which i've read is required to run the offline defrag.
The database is about 17gb and we want to shrink it down using eseutil /d but when i run to defrag it i get the following error:

Operation terminated with error -327 (JET_errBadPageLink, Database corrupted) af
ter 50.171 seconds.


ISINTEG says there are no errors when i run it in test mode and i get another error (below) when  try to check the integrity using eseutil /g:

Integrity check completed.
Database is CORRUPTED, the last full backup of this database was on 05/15/2011 0
1:00:15
Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database fi
le or corrupted db) after 1397.563 seconds.

The db store mounts fine and we don't appear to be having issues with the database when it's in use, we are just looking save some space and compact the database.  We also thought this would help with a migration to a new server that is going to happen in a month or so...

I don't want to run eseutil /p and run the risk of potential data loss since the store mounts fine and seems to work ok.  

Is there anything else we can try to get this defragmented offline or is it really not necessary since we will be migrating to the new server (it will be SBS 2011 with exchange) and we should just import the users/email into it that way?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Install below hot fix and then try to defrag the exchange database. installing below hot fix doesnot require to reboot of your server.

http://support.microsoft.com/kb/946111
Your integrity check is showing database is corrupt. Check your application logs event id 474 is might be occurring on your server.
Log Name:      Application
Source:            ESE
Date:                3/7/2011 2:49:25 AM
Event ID:         474
Task Category: Database Page Cache
Level:                Error
Keywords:         Classic
User:                   N/A
Computer:           STPSBS01.unitedtc.unitedtrustco.com
Description:
MSExchangeIS (2388) First Storage Group: The database page read from the file "E:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb" at offset 5784059904 (0x0000000158c1c000) (database page 706061 (0xAC60D)) for 8192 (0x00002000) bytes failed verification due to a page checksum mismatch.  The expected checksum was -6689073413676838281 (0xa32ba32ba5485277) and the actual checksum was -7727450446969305705 (0x94c294c2a0f60597).

Also run the chkdsk on your database drive if it reports file system errors then you need to run chkdsk /f on your exchange database drive to fix the file system error.

To resolve this issue you need to run eseutil /p then eseutil /d then mount and dismount database and then run isinteg -s server name -fix -test all tests.
Don’t worry to run eseutil /p. First take the offline backup of exchange database after dismount and then run the eseutil /p command. After completion of repaired of exchange database if you realize your database is lost. Then you can mount the database which you taken backup before proceeding hard repair.
I don’t think it will create any issue because you already ran isinteg in read only mode and not found any logical corruption.

I QasmiTechnical Lead

Commented:
1) Check to see if the Antivirus exclusion is set for the Exchange folders.
2) Also check the drive on which Exchange database is located with CHKDSK  parameters
3) If you find any errors then Run CHKDSK/F in fixing the Disk Issue first then proceed with
the Database Corruption issue.

Author

Commented:
Thank you for the solution on this.
We were concerned that there would be data loss but it appears everything went fine per the instructions you posted.   We, of course, made backups if there are any issues reported from users during production business hours but all appears to be ok  now.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial