Explanation of EV queues

[John_F2011]

Running EV 7.5 on Windows 2003.

Within Computer Management, I notice there are lots of different EV queues.

EV Archive agent admin queue

EV Default Admin queue

EV Mailbox Task for server1 admin queue

EV Restore Agent Admin queue

EV Restore spool admin queue

EV spool queue

EV storage archive

EV storage restore

Generally, the Mailbox task queue is the busiest.

Could someone explain to me what these queues mean? Is there an effect of deleting a queue if it's getting too large? Which queues are the ones we can delete etc?

[Wayne_Humphrey · Accepted solution]

Enterprise Vault Exchange Mailbox task for server queue r1:

- Retrieval ready for processing (Saveset should be available on the Spool Queue).

Enterprise Vault Exchange Mailbox task for server queue r2

- When processed the request is passed to the Storage Restore Queue (on appropriate EV server).

- Could result in multiple Retreive requests to storage restore (if users HTTP client)Enterprise Vault Exchange Mailbox task for server queue a1:

Enterprise Vault Exchange Mailbox task for server queue a1:

Pending Items that need updating. Also failed operations.

Enterprise Vault Exchange Mailbox task for server queue a2:

Individual items to process. Used for manual archive requests and whenever Enterprise
Vault cannot directly communicate with the StorageArchive queue of the Storage service.

Enterprise Vault Exchange Mailbox task for server queue a3:
Mailboxes to process. Used for Run Now archiving. 

Enterprise Vault Exchange Mailbox task for server queue a4:
Individual items to process. Only used for retrieswhenEnterprise Vault cannot directly
communicate with the StorageArchive queue of the Storage service.

Enterprise Vault Exchange Mailbox task for server queue a5:
Mailboxes to process. Used during background archiving.  
This queue is not processed outside the scheduled archiving times, so you cannot use Run Now to clear a backlog on this queue.

Enterprise Vault Exchange Mailbox task for server queue a6:
Requests to update folders with items that have been moved or copied to them. 
Enterprise Vault compresses the moved and copied item data that is placed in requests on queue A6. It also limits message storage on this queue to 100 MB. A compressed request to update 1,000 items occupies approximately 50 KB. So about 2,000 requests can be placed on the queue.  
When the queue is full, further requests are rejected. These moved and copied items have to wait for another shortcut processing run.

Enterprise Vault Exchange Mailbox task for  server queue a7:
Synchronization requests.

Storage Restore

Retrieval Request for a saveset

- When processed the saveset is passed to the Spool Queue on the server that made the retrieval request.  A Saveset available message is posted to the R1 queue onthe server that made the request.Also check the admin guide

[TonySterling]

Wayne gave you the great explaination but to your question on deleting, you shouldn't delete the because the are getting large you should determine why they are growing so large.

What queues are getting big?

[Wayne_Humphrey]

The title is Explination of Queues :)

However please read this artilce I posted a while back, it should clear any questions regardig MSMQ up.

https://www-secure.symantec.com/connect/blogs/microsoft-message-queuing-msmq

[KarlW]

Corrections to the R1 and R2 queues

R2

Retrieval requests (from client or WebApp) are placed on R2 queue.

- When processed the request is passed to the Storage Restore Queue (on appropriate EV server).

- Could result in multiple Retreive requests to storage restore (if users HTTP client)

Storage Restore

Retrieval Request for a saveset

- When processed the saveset is passed to the Spool Queue on the server that made the retrieval request.  A Saveset available message is posted to the R1 queue onthe server that made the request.

R1

Retrieval ready for processing (Saveset should be available on the Spool Queue).

Thanks

Karl

[Wayne_Humphrey]

thanks