Increase Concurrent Search session in compliance acclerator
Hello People,
EV 9.0.2 windows 2003 + CA server 9.0.2 + CA client 9.0.2
My compliance team when tries to perfrom a manual on multiple dept the manual search runs one at a time i.e if i have 5 dept and i run a manual search on all 5 dept at the same time it the search would start one a time, so once one search is completed on particular dept it would start another.
Hence i am looking for any setting where i can increase the concurrent session for manual search. I have verified the setting in CA console going in setting but haven't got more in it about the setting.
Greetings, Cdee;
Please go into the Configuration tab, then the Settings sub-tab. Hold the Ctrl key down and click on the banner where it says "Configuration Settings". Once that is done, expand the Search section by clicking on the plus sign to the left of the word "Search". Inside the Search section, look for the gray line with the option "Maximum number of consecutive searches on same index". Take note of the number shown for this setting. As part of optimizing the system, we in Support recommend setting this value to 1 so only 1 search can access an index volume. This prevents other searches from timing out when one search has an index volume that other searches need locked from those other searches. If set to 1, increase the number to 5 and restart the Enterprise Vault Accelerator Manager Service (EVAMS) on the CA server.
One thing that may help to get your searches to complete more quickly, if not already set, is to enable the Search section option "Optimize searches based on oldest and youngest items". This is not a hidden setting, so it will be shown in a white line. If not already enabled, place a check mark in that line's Value column, click the Save button, click the OK button to acknowledge the need to restart the Customer Background Task, then restart EVAMS on the CA server.
Once enabled, the "Optimize searches" option will only search against index volumes that have items within the date range of the search. This prevents searching against index volumes that we know don't have any items in the date range of the search.
