Priv1.edb has suddenly ballooned in size - from approx 20GB to 95GB, almost overnight!!

Hi there everyone, first post on EE!

Basically, we have a customer who uses SBS 2003, and their priv1.edb file has just ballooned in size from 20GB to almost 95GB, which is 20GB bigger than the theoretical maximum (after applying SP2, and changing the registry - in fact I think the registry was changed only to 60GB for the database, so even more strange).

We didn't even notice a problem until the backup failed one day, as they only have a DAT160, so 95GB + their data exceeded the amount.

The mailbox store also started dismounting itself every couple of minutes.

I have run ESEUTIL and ISINTEG to defrag and check for errors, and they both went through and nothing came up. The database remained at the 95GB mark, but when we remounted it it has not dismounted again.

ESEUTIL /P has also been run, but this didn't reduce the size either.

Another thing to note is that when I manually add up the sizes of all the mailboxes on there, it comes to about 20GB, which is the amount the mailbox store should be. So I don't know what the other 75GB is........

Is it possible to mount the database in a recovery storage group, delete the original database, and then move mailboxes into a new database? Due to it being SBS, we can't create another mailbox store. I'm not too sure about recovery storage groups...

Very strange - any ideas would be much appreciated.

Thanks in advance!!

Event viewer messages:

Event Type:      Warning
Event Source:      MSExchangeIS Mailbox Store
Event Category:      General
Event ID:      9685
Date:            16/09/2008
Time:            19:33:44
User:            N/A
Computer:      COMPANY-SERVER
Description:
Exchange store 'First Storage Group\Mailbox Store (COMPANY-SERVER)': The current physical size of this database (the .edb file and the .stm file) is 95 GB. This database has exceeded the size limit of 50 GB. However, the logical free space in this database has not yet been evaluated. Therefore, it is possible that this database contains enough free space to bring its logical size below the maximum size limit.

If the logical database size exceeds the maximum size limit, it will be dismounted on a regular basis.

For more information, click http://www.microsoft.com/contentredirect.asp.
##########################################################
Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      9518
Date:            16/09/2008
Time:            19:32:59
User:            N/A
Computer:      COMPANY-SERVER
Description:
Error 0xfffffbf8 starting Storage Group /DC=local/DC=CompanyName/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=COMPANYNAME/CN=Administrative Groups/CN=first administrative group/CN=Servers/CN=COMPANY-SERVER/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.

For more information, click http://www.microsoft.com/contentredirect.asp.
##########################################################
Event Type:      Error
Event Source:      ESE
Event Category:      General
Event ID:      482
Date:            17/09/2008
Time:            02:25:20
User:            N/A
Computer:      COMPANY-SERVER
Description:
Information Store (6760) First Storage Group: An attempt to write to the file "D:\Exchange\Exchsrvr\MDBDATA\E00tmp.log" at offset 0 (0x0000000000000000) for 1048576 (0x00100000) bytes failed after 0 seconds with system error 112 (0x00000070): "There is not enough space on the disk. ".  The write operation will fail with error -1808 (0xfffff8f0).  If this error persists then the file may be damaged and may need to be restored from a previous backup.

For more information, click http://www.microsoft.com/contentredirect.asp.
##########################################################Start Free Trial