I try to set up journaling in my Exchange 2013. I've created mailbox and turned on journaling feature that send all email to this mailbox. Mailbox located in separate database on separate Exchange 2013 server.

Why after 1 days journaling mailbox size is 20 Gb and database size (.edb file) is 200 Gb? Why database grow so fast and where is remaining 180 Gb? On second day  I moved mailbox to new database and new .edb was 20 Gb. After 12 hours mailbox size is 30 Gb and .edb file is 120 Gb.

What should I do to slow database growing?

Hello,

Based on my knowledge,  EDB size=Size of Mailboxes + Size of Retention Mail Items + Size of Retention Mailboxes + White Space

If you don't have any deleted items and deleted mailboxes, mailbox size should be close to DB size.

How did you check the mailbox size in Exchange 2013?

Could you screenshot the command output in your next post?

Thanks,

Evan

This is how I get mailbox size:

.edb file now over 300 Gb and I now moving mailbox it to new database to save disk space.

Hi Qwadrat,

I am running into the same issue. Did you manage to solve it?

Currently I am currently increasing my JournalDB with 10 GB per hour althought the Mailbox just has 200 MB.

Regards

Stephan

1. Are you saying that ONLY ONE mailbox is being journaled?
2. is your system completely patched?

Hi Troy,

Sorry that about the misunderstanding.We have currently 7 Mailboxes on a dedicated User Mailbox Database. and 1 Mailbox (the journal Mailbox) on a dedicated "Journal Mailbox Database". So we are journaling 7 Mailboxes. These 7 Mailboxes have around 9 GB of total mail items.

The User Mailbox Database increases on a "Normal" level. (currently at 11GB) The Journal Mailbox on the other hand increases in a drastic way. Yesterday we had to disable journaling as our 150 GB dedicated LUN filled up with a 500 MB size Mailbox in it.

The System is completly Patched.

• Edited by Stephan Cologne 14 minutes ago

Hi Troy,

Sorry that about the misunderstanding.We have currently 7 Mailboxes on a dedicated User Mailbox Database. and 1 Mailbox (the journal Mailbox) on a dedicated "Journal Mailbox Database". So we are journaling 7 Mailboxes. These 7 Mailboxes have around 9 GB of total mail items.

The User Mailbox Database increases on a "Normal" level. (currently at 11GB) The Journal Mailbox on the other hand increases in a drastic way. Yesterday we had to disable journaling as our 150 GB dedicated LUN filled up with a 500 MB size Mailbox in it.

The System is completly Patched.

• Edited by Stephan Cologne Friday, June 05, 2015 7:14 AM

Hi Troy,

Sorry that about the misunderstanding.We have currently 7 Mailboxes on a dedicated User Mailbox Database. and 1 Mailbox (the journal Mailbox) on a dedicated "Journal Mailbox Database". So we are journaling 7 Mailboxes. These 7 Mailboxes have around 9 GB of total mail items.

The User Mailbox Database increases on a "Normal" level. (currently at 11GB) The Journal Mailbox on the other hand increases in a drastic way. Yesterday we had to disable journaling as our 150 GB dedicated LUN filled up with a 500 MB size Mailbox in it.

The System is completly Patched.

• Edited by Stephan Cologne Friday, June 05, 2015 7:14 AM

Okay, I am one step further.

I saw that I have several Mails inside my queues which cannot be transmitted into the journal Database.

Once I deleted those. The massive increase stopped. Now I just have to see why these are not beeing processed.

Here is the error: (I guess it is related to the missing from address)

Identity: tt-col-s248\3\6047313952802
Subject: Unzustellbar: Cron <xx@xxx> /usr/local/bin/clk_backup_to_tar_diff
Internet Message ID: <f67a6c96-7ea1-4304-9392-9877a543474c@journal.report.generator>
From Address: <>
Status: Wiederholen
Size (KB): 9089
Message Source Name: Journaling
Source IP: 255.255.255.255
SCL: 0
Date Received: 08.06.2015 06:50:19
Expiration Time:
Last Error: 400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:MessageSubmissionExceededException.MapiExceptionMaxSubmissionExceeded; Failed to process message due to a permanent exception with message Cannot save changes made to an item to store. 16.55847:4D100000, 17.43559:0000000094000000000000000000000000000000, 20.52176:000F34840900000000000000, 20.50032:000F34847917000000000000, 255.23226:000F3484, 255.27962:0A000000, 255.27962:0E000000, 255.31418:09000000, 16.55847:F2000000, 17.43559:000000001801000000000000E401000000000000, 20.52176:000F34840900F01F2C000000, 20.50032:000F348479170010000F3484, 255.23226:07000000, 255.27962:0A000000, 255.27962:0C000000, 255.17082:DA040000, 0.18273:0A000000, 4.21921:DA040000, 255.27962:FA000000, 255.1494:00000000, 5.59176:0000A0004C696D69746174696F6E000000000000, 5.34600:CF9D1B0143757272656E7453697A650000000000, 4.42792:DA040000, 1.63016:0C000000, 4.39640:DA040000, 5.10786:0000000031352E30302E313037362E3030303A74742D636F6C2D73323438000000000000, 255.1750:2C000000, 255.31418:00000000, 0.21457:00000000, 4.19665:DA040000, 0.37632:00000000, 4.37888:DA040000 [Stage: CreateMessage]. The failure was replaced by a retry response because the message was marked for retry if rejected.
Queue ID: xxx\3
Recipients:  xxx@xxx;3;3;[{LRT=};{LED=400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:MessageSubmissionExceededException.MapiExceptionMaxSubmissionExceeded; Failed to process message due to a permanent exception with message Cannot save changes made to an item to store. 16.55847:4D100000, 17.43559:0000000094000000000000000000000000000000, 20.52176:000F34840900000000000000, 20.50032:000F34847917000000000000, 255.23226:000F3484, 255.27962:0A000000, 255.27962:0E000000, 255.31418:09000000, 16.55847:F2000000, 17.43559:000000001801000000000000E401000000000000, 20.52176:000F34840900F01F2C000000, 20.50032:000F348479170010000F3484, 255.23226:07000000, 255.27962:0A000000, 255.27962:0C000000, 255.17082:DA040000, 0.18273:0A000000, 4.21921:DA040000, 255.27962:FA000000, 255.1494:00000000, 5.59176:0000A0004C696D69746174696F6E000000000000, 5.34600:CF9D1B0143757272656E7453697A650000000000, 4.42792:DA040000, 1.63016:0C000000, 4.39640:DA040000, 5.10786:0000000031352E30302E313037362E3030303A74742D636F6C2D73323438000000000000, 255.1750:2C000000, 255.31418:00000000, 0.21457:00000000, 4.19665:DA040000, 0.37632:00000000, 4.37888:DA040000 [Stage: CreateMessage]. The failure was replaced by a retry response because the message was marked for retry if rejected.};{FQDN=};{IP=}];0;CN=......

Sorry for the delayed response I was out of town and am now trying to get caught up.  Yeah so you basically had a bad message bouncing around the queue.   It appears that there have been similar issues with Exchange 2007 and 2010 but UI have not yet found anything with 2013.   

I am searching with these strings

• "the failure was replaced by a retry response because the message was marked for retry if rejected"
• "STOREDRV.Deliver.Exception:MessageSubmissionExceededException.MapiExceptionMaxSubmissionExceeded"

And it appears the common issues I was finding are that 

• it was fixed with a patch so is your server 100% patched with the latest updates for Exchange?
• OR the message or attachment size hit a limit