EV: 10.0.4.1189
Exchange 2010: 14.03.0158.001
Windows Server 2008 R2 Enterprise SP1
I am getting alerted to the issue based on the mailbox database size set for the journal . There are no errors reported regarding the journal task itself, but it is obvious that items are not completely archiving. Viewing the journal mailbox through outlook shows about 92,000 items Pending Archive Part, and 6800 Pending Archive. Unarchived items continue to grow at a steady rate. Restarting the journaling task will start moving some items for a few minutes, until archiving seems to just stop. (after restarting the task, items with the message class will go down, pending archive will rise and fall, and pending archive part will rise and fall, then after a few minutes, the pending archive and pending archive part stop moving and message items increase. This looks like it is finally going in the right direction after restarting the storage service. This has happened to me about 3 times in the last month, where I have had to restart the storage service to get the journaling task to run normally.
There were no obvious events in the event log relating to this issue on the EV server.
DTrace of the Journal Task shows the following;
<JournalTask> <6656> EV:H {CArchivingAgent::QueueEligibleItem} HREX fn trace : Error [0xc0040b31], [.\ArchivingAgent.cpp, lines {25004,25034,25054,25062},built Jul 10 17:51:28 2013].
<JournalTask> <10364> EV:H {CArchivingAgent::QueueEligibleItem} HRXEX fn trace : Error [0xc0040b31], [.\JournalPart.cpp, lines 413,477,488,509,521,1020}, built Jul 10 17:5128 2013].
and
<JournalTask> <18816> EV:M {CSorageArchive::GetVaultStatusEx:#764} Modifying throttle status for archive [####################VAULT] from [DV_DS_AS_AVAILABLE (1)] to [DV_DS_AS_STORAGE_QUEUES_FULL (6)].
For the first errors I found this article http://www.symantec.com/connect/forums/archivingjournal-task-will-pause-let-it-recover-0xc0040b31, but the links to support materials are no longer valid.
For the second message, I found an article http://www.symantec.com/business/support//index?page=content&pmv=print&impressions=&viewlocale=&id=TECH173570
Has anyone else experienced similar situation? The best advice I got was to bounce the services every once in a while.