Forum Discussion

GianniCool's avatar
GianniCool
Level 6
15 years ago
Solved

Purging the MSN queue

Is it recommended to purge 8,600 pending items for archive?  I had SQL Deadlock errors that have since been cleared by a DBA.  However, all the archiving jobs have the pending icon beside them.  I have read the following docs: Document ID: 287877, Document ID: 31676, Document ID: 273157.

What is recommended?

-John
Enterprise Vault
Information Governance
Performance
  • JesusWept3's avatar
    JesusWept3
    15 years ago
    well if the item is in the A2 , the items have not been yet archived, as they will go from A2 to the storage queue, once it has been processed from storage queue, that means it will have been archived and eventually added to the index.

    The real problem with this is, it's not just those 8600 items you have to be concerned about, its other items that are genuinely pending and awaiting backup that you need to be worried about, if you do a pending shortcut timeout, then they will be re-archived and re-indexed.

    I would still suggest looking at the MSMQ Storage locations, seeing how big its gotten, if its over 1gb then you will have to increase the quota to 8GB and then try again, hopefully this will get things moving in and out of the queue



  • GianniCool's avatar
    GianniCool
    Level 6
    15 years ago

    Evault Rookie, I can't see your comments anymore.  I set the reg entry to "0", set the archiving to "Read Only", and then restart the services?
  • AndrewB's avatar
    AndrewB
    Moderator
    15 years ago
    What queue are the items in? A5 is safe to purge and you do not need to set your indexes or stores to RO.
  • Evault_Professi's avatar
    Evault_Professi
    Level 6
    15 years ago

    My apologies I wasn't sure if your question had applied to Exchange archiving with Evault.


    If so, once you set the policy setting "Pending Shortcut Timeout" value to 0, amended the archive task to"Read Only" mode and restarted the archive task. The pending archive icon should be restored. Once this is confirmed...remove the "Read Only" option under the properties menu of the task and restart the archive service again.

    Please advise...
    Thanks,
    Dennis
    STS Symantec Enterprise Vault 2007
    STS Symantec Enterprise Vault 8.0 for Exchange

  • JesusWept3's avatar
    JesusWept3
    Level 6
    15 years ago
    Honestly i wouldn't do a Pending Shortcut timeout if you can help it as in certain configurations (i.e After Backup) you will end up with duplicates. I'd sooner find out why EV isn't processing the 8200 emails that are stuck in the A2 queue, maybe you've breached the default 1GB limit for MSMQ? maybe its stuck trying to process email for a user that is no longer on that exchange server etc? Would highly suggest this product: http://www.cogin.com/mq/?c=1&gclid=CMWk-c2d8KACFcN05Qod9xEiFw That way you can move/delete individual messages as opposed to blasting an entire queue
  • RahulG's avatar
    RahulG
    Level 6
    15 years ago

    Its not recommended to purge the queue ,but incase if there is some issue you have to purge it . Check if the email which are in pending state have been archived or not .....you can check this by using search or archive explorer..if the item does not exist you can change the set the pending shortcut timeout setting in the policy and change the item back to normal from the pending state .  Purging the a1 queue have issue like you get duplicate entries for the archived item .

  • JesusWept3's avatar
    JesusWept3
    Level 6
    15 years ago
    well if the item is in the A2 , the items have not been yet archived, as they will go from A2 to the storage queue, once it has been processed from storage queue, that means it will have been archived and eventually added to the index.

    The real problem with this is, it's not just those 8600 items you have to be concerned about, its other items that are genuinely pending and awaiting backup that you need to be worried about, if you do a pending shortcut timeout, then they will be re-archived and re-indexed.

    I would still suggest looking at the MSMQ Storage locations, seeing how big its gotten, if its over 1gb then you will have to increase the quota to 8GB and then try again, hopefully this will get things moving in and out of the queue



  • GianniCool's avatar
    GianniCool
    Level 6
    15 years ago
    Thanks JW!  We ended up increasing the quota to 8Gb.

    Thanks EV Forum!

    -John