troubleshooting Question

SBS2003 Exchange Database Corrupt and Log files filling hard drive.

Avatar of VitalNetworkSolutions
VitalNetworkSolutionsFlag for United Kingdom of Great Britain and Northern Ireland asked on
ExchangeSBS
17 Comments1 Solution875 ViewsLast Modified:
Hi,
I have curently taken over a SBS2003 server and have came across a big problem with their exchange database;

They use Veritas backupexec 10 for SBS but for some time they have only been backing up at brick level. The log files in MDBDATA have mounted up until they are nearly filling the hard drive.
I ran a full backup on the database but it failed to remove the log files and threw up the following errors;
___________________________________________________
Event Type:      Information
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      225
Date:            05/09/2011
Time:            22:59:35
User:            N/A
Computer:      SERVER2003
Description:
Information Store (6168) First Storage Group: No log files can be truncated.  

For more information, click http://www.microsoft.com/contentredirect.asp.

___________________________________________________
Event Type:      Error
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      217
Date:            05/09/2011
Time:            22:26:50
User:            N/A
Computer:      SERVER2003
Description:
Information Store (6168) First Storage Group: Error (-1018) during backup of a database (file C:\Program Files\Exchsrvr\mdbdata\priv1.edb). The database will be unable to restore.

For more information, click http://www.microsoft.com/contentredirect.asp.

___________________________________________________
Event Type:      Error
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      474
Date:            05/09/2011
Time:            22:26:46
User:            N/A
Computer:      SERVER2003
Description:
Information Store (6168) First Storage Group: The database page read from the file "C:\Program Files\Exchsrvr\mdbdata\priv1.edb" at offset 9787383808 (0x00000002475fa000) (database page 2389497 (0x2475F9)) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch.  The expected checksum was 8080038126035932732 (0x70220fdda1fc163c) and the actual checksum was 3166078850964650706 (0x2bf02bf0ba9ffad2).  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.

For more information, click http://www.microsoft.com/contentredirect.asp.
___________________________________________________
I tried using NTBACKUP also but that didn't work either. it stopped about 20% into the backup procedure.

I have looked into using ESEUTIL to do a repair, defrag and then ISINTEG but I have a few concerns.

Firstly, the space on the drive is too low, I believe you need about 20% of the database size (the database is 47Gb) to run the ESEUTIL repair. then at least 110% of the database size for the defrag.
Secondly, the time it will take. again I read it can be 1hour for 1gb. This means nearly two days for this database. Downtime they can ill-afford.
Finally will ESEUTIL/ISINTEG work for this issue. Can I simply copy the database files and if the process fails put them back. thenat least I can start from scratch.

I have though about doing the following;

Install a second temporary exchange server, move the mail boxes into a new mailbox store on that server.Delete the original corrupt database on SBS 2003, recreate a new one, then move the mailboxes back to the newly created mailbox store on the SBS2003.

or,

Export all mailboxes into PST files. Recreate a new mailbox store on the SBS2003 and import back in. Could be very long process.

or,

Can a copy of the database put on a diferent non exchange machine, which has more space and do the ESEUTIL/ISINTEG there? this would allow me to test the process (duration and success) and keep the original databse running during the test.

or,

Is there a way to remove the log files without affecting the database, then I can deal with the corruption with more HD space?

Any advice would be grateful.

Kind Regards,

Colin
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 17 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 17 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros