Hello
I'm trying to find a good workflow technote on EV journalling to help troubleshoot a slow journal archiving scenario.
Is there anything around that could help?
Essentially we're testing a single journal arhcive that recieves about 4 messages a second (about 15k per hour). I was expecting the EV server to keep pace with this over a 24Hr period but finding that even after 1 hr it falls woefully behind and before long the number of IPM.Note messages raises above 1000 which has the effect of causeing the pending items never to be removed from the journal mailbox - Symantec say this is a hard-coded limit - which subsequently causes journal issues with Exchange.
A Dtrace run by Symantec has shown that the EV server is archiving about 1 item every 2 seconds
Symantec have offered several opinions - They said the issue is with the Hub Transport server causing a bottle neck as Exchange passes the messages back through the HT server when EV archives the items....!? really? I can't see any connection with archiving items from the Journal mailbox and the HT server - surely once the email is in the journal mailbox the HT server is no longer in the equation - but happy to stand corrected.
They also say that another EV Journal server could help - but looking at the resources of the current journal server it's bearly breaking a sweat when looking at CPU and RAM.
Also the SQL server is also good as far as CPU/RAM/Network goes.
Should I be concentrating on Disk IO (EVserver or SQL server?)? Message Queues (which ones)? Disk IO on message Queue disk?
From what I can see visually the items change from IPM.Note to Pending Archive pretty quickly but then spend an age being deleted from the mailbox - so what is EV doing during the part of the process?
There are probably lots of things that can cause archiving to be slow so I guess I'm just after a set of logical steps to narrow things down - hence why I thought some kind of process flow would be a good place to start.
thanks in advance