Exchange store dismounted after reaching 129GB

One of the servers has managed to reach 129GB exchange store size, the limit set is 75GB. all had been working fine untill 11.51pm last night an event was recorded with ID 1159 'Database Error 0xfffffd9a occured in function JTAB_BASE::EcSetColumn while accessing the database'. From that point onward the event log records lots of MAPI session errors.

For some reason the exchange store has increased in size by nearly 100GB overnight, its not something I have seen before. I am opening a call with Microsoft regarding this but in the meantime, does anyone know about this issue or experienced it before?
PowerhousecomputingAsked:
Who is Participating?
 
B HCommented:
how do you feel about deleting the store, creating a new one, and pushing your backups into the new one?
0
 
B HCommented:
i've seen it with a looping rule that got stuck in someone's outlook, essentially creating the same object over and over... take a look at the users mailboxes size and see who's 120gb
0
 
Alan HardistyCo-OwnerCommented:
The 75Gb file size is a virtual size, not a physical size.
You may have plenty of white space within the file and thus it could be 129Gb and still not have 75Gb of mail in it as it could have 54Gb of white space!
Increasing in size by 100Gb overnight is rather unusual - you may want to set your store retention to Zero and then run a defrag of the file with eseutil /d to remove the white space, but check your event logs for event id 1221 to see how much white space is in the file first (usually runs at about 5:00am).
Microsoft should be able to sort you out as they can logon remotely and see what is happening - we are not able to.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Glen KnightCommented:
Will the mailbox store mount at all?
This sort of thihng is normally caused by:

a) a bad rule that is bouncing mail and receiving NDR's etc
b) antivirus/SPAM software
c) POP3 service downloading duplicate e-mails (only availble in SBS)

Check the mailbox sizes and see if there are any that seem unusually large, specifically the administrator mailbox
0
 
PowerhousecomputingAuthor Commented:
The mailbox does mount, I will have a look through your suggestions. Thanks
0
 
PowerhousecomputingAuthor Commented:
The exchange store has now grown to 146GB, I've been looking on experts exchange and have found posts relating to defragmenting the exchange store, the online defrag detected 18GB of free space. However, I have read on MS that you need 110% (spacewise) of the exchange store in free space in order to perform a defrag. as a result of the exchange store growing I now no longer have anywhere near that amount of space on the server to perform the offline defrag. Is there anyway around this?
0
 
PowerhousecomputingAuthor Commented:
I'll give that idea some thought. I may have to get the users to back up mail on individual workstations for the past few days as the backup has cancelled due to going over tape size.
0
 
Glen KnightCommented:
A defrag is not going to help neither is deleting your store.

You need to find out where the messages are coming from.

My advice would be to set mailbox limits on the mailbox store so that users cannot send and receive mail once they reach a certain size.if the store is growing that rapidly you must be able to see the mailboxes growing?
0
 
PowerhousecomputingAuthor Commented:
Thats the strange thing, the mailboxes or the public folders haven't grow in size, they are pretty much the same as they were this time last week.
0
 
PowerhousecomputingAuthor Commented:
Here you can see what I mean:
Mailbox-Size.jpg
0
 
PowerhousecomputingAuthor Commented:
Microsoft gave me support on this one, it was a corrupt database creating hundreds of log files, we had to remove the old database, create a new one, add the old database to a recovery storage group and then recover the good mailbox data.
0
 
PowerhousecomputingAuthor Commented:
This is pretty much what we had to do!
0
 
PowerhousecomputingAuthor Commented:
Also as a note, the event id1159 occurs when the database has created 1009 log files and automatically dismounted itself, this happened on ths server because the backup locked the database to backup as per usual but the large numbers of log files being generated caused it all to crash
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.