asked on Defragging an exchange 2003 database
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,
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?
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,
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?
ExchangeEmail Servers
Last Comment
thecomputerplace
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
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.
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.
ASKER
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.
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.
http://support.microsoft.com/kb/946111