Forum Discussion

Rob_dos_Ramos's avatar
Rob_dos_Ramos
Level 6
13 years ago

Exchange 2010 Journaling PendingArchive Part

Hi All

We have enabled journaling for a customer and we are seeing a large number of PendingArchive Part messages in the outlook profile.

EV server is 9.0.3 and it is on a windows server 2008 R2 SP1, 8 CPU (2.4GHZ) 24 GB ram, 64 BIt, VMware server.

 

We have about 48000 items PendingArchive Part and they are taking a very long time to come down. Is there a way of speeding up the process or might there be a problem with the journaling?

We need your urgent assistatnace as this is less then half the organization that has been enabled and we need to get Journaling up and running.

I have enabled the JournalDelay registry value to '2' as per http://www.symantec.com/business/support/index?page=content&id=TECH61066&actp=search&viewlocale=en_US&searchid=1330712314483

Still no luck.

Any comments or ideas would be greatly appricated.

Thank you

Rob

Enterprise Vault
Information Governance
Performance
Troubleshooting
  • Prone2Typos's avatar
    Prone2Typos
    13 years ago

    So by teh design this is somewhat expected behavior. You need to note the time and date, if the items ever clear, clear slowly, or what the deal is in it. I have not seen anything implying that ... althogh I did review. Keep in mind that cycling the sercives will restart the review process and this is one of those issues that you have to step away from for a while to see it have a positive response.

     

    I have seen Exchange issus causing an issue, I have seen EV communication issues be related, and most recently... cached credential on the EV server relaing to the Journal performance. If you were haivng an issue communicating with the Exch Server, you should also see that manifest in the Archive task and it doing less than expected.

     

    The concurrent connections depends on a lot of env and sizing things... so I would not say there is a best practice outside of default. Keeping it as low as possible has typically been a cheap way to get out of fixing an issue (IMHO) and I would say is less than ideal. This is something that needs to be tuned, monitored, adjusted, and retuned to best suit your systems needs.

     

    Really to have an idea as to what is happening.. A DTrace is needed against the Journal task for ... I would say 15 minutes. You can use Pastepin or attache the log... please dont copy the contents of the trace into the forums... that drives me nuts personally.

     

    In a rare condition, I have seen some third party product (like antivirus on the Exchange server) modify the time stamps on these messages... which in turn causes them to never archive.

     

    I hope this helps. If you have had this resolved (as it has been a while since it was updated) please update the posting with teh resolution or mark the person that helped you as resolving it so that those out here to help can direct their attention to those who need it most.

     

    Many thanks.

17 Replies

Sort By
Show More
  • Rob_dos_Ramos's avatar
    Rob_dos_Ramos
    Level 6
    13 years ago

    Hi AKL

    Ok all the reg keys are set as per your post. no load balancing is in place. we are not using a host file.

  • AKL's avatar
    AKL
    Level 6
    13 years ago

    So how are new items in journal mailbox looking - aren they getting archived? I will also recommend to create some secondary journal mailboxes to clear out backlog.

  • John_Chisari's avatar
    John_Chisari
    Level 6
    13 years ago

    +1 for AKL's suggestion, it's probably the only way you are going to get through that backlog - apart from setting JournalDelay to 0, which is not recommended as there will be no grouping of email by MessageID anymore, causing duplicates in the archive.

    And also, don't restart the archive task for that journal mailbox, as EV will just start again from the top.

  • Bruce_Cranksh1's avatar
    Bruce_Cranksh1
    Level 6
    13 years ago

    I am also seeing this issue recently at a customer. The Journal Mailbox suddenly slows down. There are no errors. I logged a call with support and despite all the suggestions after Dtrace and other steps the only working solution was to create another Journal mailbox. We did this but to be honest its not really a  solution that installs confidence going forward

  • RahulG's avatar
    RahulG
    Level 6
    13 years ago

    You may check if the item which are in pending state have been archvied or not . you simply make a serach in the journal archvie to check . If the item is not archvie you may try cancelling the pending item as it would not cause duplicate items in the archive . 

  • Prone2Typos's avatar
    Prone2Typos
    Moderator
    13 years ago

    So by teh design this is somewhat expected behavior. You need to note the time and date, if the items ever clear, clear slowly, or what the deal is in it. I have not seen anything implying that ... althogh I did review. Keep in mind that cycling the sercives will restart the review process and this is one of those issues that you have to step away from for a while to see it have a positive response.

     

    I have seen Exchange issus causing an issue, I have seen EV communication issues be related, and most recently... cached credential on the EV server relaing to the Journal performance. If you were haivng an issue communicating with the Exch Server, you should also see that manifest in the Archive task and it doing less than expected.

     

    The concurrent connections depends on a lot of env and sizing things... so I would not say there is a best practice outside of default. Keeping it as low as possible has typically been a cheap way to get out of fixing an issue (IMHO) and I would say is less than ideal. This is something that needs to be tuned, monitored, adjusted, and retuned to best suit your systems needs.

     

    Really to have an idea as to what is happening.. A DTrace is needed against the Journal task for ... I would say 15 minutes. You can use Pastepin or attache the log... please dont copy the contents of the trace into the forums... that drives me nuts personally.

     

    In a rare condition, I have seen some third party product (like antivirus on the Exchange server) modify the time stamps on these messages... which in turn causes them to never archive.

     

    I hope this helps. If you have had this resolved (as it has been a while since it was updated) please update the posting with teh resolution or mark the person that helped you as resolving it so that those out here to help can direct their attention to those who need it most.

     

    Many thanks.