UNSOLVED
SourceOne Jounaling
I am experiencing problems with the journaling task. In the last few days the speed of archiving messages has dropped dramatically, with the result being a large build-up of messages in the SourceOne Inbox. An EMC support engineer has checked over my system and was unable to find a solution. He has confirmed that there are no problems with SourceOne, apart from the slow journaling. He was also able to tell me that the Archive db is fragmented. Any suggestions would be appreciated.
To answer your questions:
1. The Message Center disk has 83% free space
2. EMC support guy determined that the SQL Archive db was 99% fragmented
3. We are on v6.8.1.1073
4. The EMC guy checked the ExJbJournal.exe.log file yesterday
5. We have about 5000 users on the system. There are no rules in place. We only have one Journal mailbox and one archive folder.
RKatwal
2 Intern
•
600 Posts
2009
0
Posted June 24th, 2013 17:00
Greetings,
There are many factors that may impact the ingestion speed. Since all details of your environment are not mentioned, I will list a few for you things to watch for:
1. Disks hosting Message Center could be struggling and cannot cope up with load.
2. SQL Es1Archive DB fragmentation.
3. Version of ES1, as long back in 6.6.Sp1 there was an SP that needed to be modified if SQL side deadlocks were seen. Latest versions available do not have this issue.
4. Sometimes there could be an archive server that is having some issues, what workers do is, they send messages in RPC packets to servers with Archive role. If a server is having some kind of network issues or other issues and it is an archive server that can cause jobs to hang because it never or after long delay will reply back to the RPC call. It could be ruled out by checking ExJbJournal.exe.log files when trace verbosity is set to 4.
5. Would you know how many users you could be archiving and how many archive folders you have ? Are there rules in place ? When an email is sent to large number of users, in exchange gets broken down into multiple journal messages and end up in all journal mailboxes, while processing this message journal jobs may slow down for some time. It will depend on how many copies of the messages and archive folders are there to archive to, everything will come to normal state after few hours. This condition can also be seen in the ExJbJournal.exe.log files. It will only be seen mainly when you have large number of journal mailboxes on exchange being archived.
6. Check performance of the SQL side of things to make sure everything is fine on SQL side.
In most of the cases support should be able to help. Would you know if support personnel engaged next level support ? If possible can you please send me SR# in the private message ? We will make sure it gets looked into.
Thanks,
Rajan