Solved

Exchange SBS2003 database over limit.

Posted on 2015-02-17
8
33 Views
Last Modified: 2015-05-17
Hi all,

we have one SBS2003 with 30 mailboxes and yesterday is noticed that  EDB is 39GB and STM 38GB.
Store was unmounted and eseutil /d was started.

this is output:
Operation terminated with error -1018 (JET_errReadVerifyFailure, Checksum error on a database page) after 11811.32 seconds.

After isinteg with fix switch  , eseutil was tryed again with same result.

In all backup instances databases are in same state.

However, everything is working in this moment and clients are instructed to archive all mails to .PST
After that, idea is to delete storage group  or mailbox store, create new one and everything should be fine.

I need help how to delete, create new storage grout or mailbox store and attach clients!
Many thx
0
Comment
Question by:bbmservis
8 Comments
 
LVL 4

Expert Comment

by:Manoj Bojewar
ID: 40613731
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40613901
Why not increase the size limit of the database? Providing you've got SP2 for Exchange 2003 installed, you can increase the database size limit up to 75GB. That should prevent this from occurring again in the near future. See this article for the steps to do this: http://support.microsoft.com/kb/912375
0
 

Author Comment

by:bbmservis
ID: 40614925
@VBITS

It is already 75GB, Exchange looks combined size od EDB and STM.
0
 

Author Comment

by:bbmservis
ID: 40615015
@Manoj

Hm,,is this only sollution?
I do have fully working Exchange, i mean still it is. Restoring from backup is not an option because databases in backup are in same state as this working one.

All clients have all mails in archive.pst on workstations. I need empy mailboxes, a fresh start!

thx
0
Why do Marketing keep bothering you?

Is your marketing department constantly asking for new email signature updates? Are they requesting a different design for every department? Do they need yet another banner added? Don’t let it get you down! There is an easy way to manage all of these requests...

 
LVL 24

Expert Comment

by:VB ITS
ID: 40615902
Yes of course. Sorry bbmservis I didn't see the size of the STM file when I originally read your question.

You can look at performing a hard repair of the database, i.e. use eseutil with the /p switch to bring the database back online. Before you do this though, it is best you have a read of this article from Microsoft to understand the ramifications of using the /p switch: http://support.microsoft.com/kb/259851

Your other options are to use a third party program to pull out data from the corrupted .EDB file to put into a new database, or use third party software to convert each user's OST files into PST files and create the new storage group in Exchange.
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 40616627
Are you archiving data off...then cleaning up the database?
If this were my client, we'd archive everything but the last 12 months.   Get the database back online.
Then immediately look for a new email solution
Exchange 2003 is out of support.  If things go terribly bad, you can't call MS for help...period.
Windows Server 2003 reaches end of life this summer (July)
0
 

Accepted Solution

by:
bbmservis earned 0 total points
ID: 40620734
Chris & VB ITS,

Im archiving all from mailboxes to archive.pst. After confirmation that everything is in .pst-s gonna  try repair database, eseutil /p.

If unsuccesfull then im gonna try this:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_26314496.html

Clean start for all users, only thing that worries me :  what about client outlooks, when they start them up and try to connect to mailbox? Do i have to recreate something in Exchange features on user properties or Outlook can automaticly start to work online again?
0
 

Author Closing Comment

by:bbmservis
ID: 40781536
None of those above were helpfull.
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

Suggested Solutions

Check out this infographic on what you need to make a good email signature that will work perfectly for your organization.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video discusses moving either the default database or any database to a new volume.

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now