Enterprise Vault Storage Queue stops processing items after Building Block Failover.

Problem

After fail over of an EV server to secondary server in a building blocks configuration, the storage queue stops processing items for the failed over vault stores. This is due to continuous insertion of by archiving task (or any other ingestion method) the storage queue reaches its maximum length thus doesn't accepts any new items.
 

Error Message

Following warning may be seen once storage queue reaches to maximum length.

Event ID:      29000
Task Category: Storage Online
Level:         Warning
Keywords:      Classic
Description:
Item has not been added to the storage queue because the queue has reached its maximum length. Enterprise Vault will automatically try again later.

V-437-2900

Cause

The storage queue feature introduced with Enterprise Vault Version 11.0 and Later, every record inside the storage queue location is associated with vault store and StoragServiceEntryID of the active EV server. After a building block fail over to secondary server, the storage queue will only process items failed over to the new local storage service, thus the items created by prior to fail over will accumulate in storage queue location and never process.

Workaround
When failed over, it is recommended to keep all vault stores in backup mode.
 

Solution

This issue has been addressed in the following release:

Enterprise Vault 11.0.1 Cumulative Hotfix 4 Release and higher
https://www.veritas.com/support/en_US/article.100031905.html

Enterprise Vault 12 release
http://www.veritas.com/docs/000099905
Note: For information on how to obtain Enterprise Vault 12 see: How to obtain the license key and installation download for Veritas products