Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Large Advanced Search in batches by archived date?

Updated: 07 Jun 2010 | 2 comments
ANDREY FYODOROV's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi all.

I am trying to search a large vault (~1000 PSTs of users who left the company through the years were archived into this vault).

When I put in my search criteria and click Search, instead of showing me all the results, it gives me a drop down menu with ranges of dates, by archive date.

There aren't that many search results actually.

It is pretty inconvenient though that they get broken up like this (trying to add them all into one basket et al)

Is there any way to stop this behavior?

Thanks!

Comments

MichelZ's picture
26
Mar
2009
0 Votes 0
Login to vote

Haven't seen this yet, could

Haven't seen this yet, could you attach a screenshot of it?

www.quadrotech-it.com - All your EV Tools | www.techfreak.ch

Paul Grimshaw's picture
26
Mar
2009
1 Vote +1
Login to vote

This is correct behavior and

This is correct behavior and is due to a concept called federated search. You are seeing the date ranges because your archive has more index volumes than federated search will allow. The default is 5.

In order to control “federated searching” there are some settings that can be placed within the WebApp.ini file
·         FederatedSearchMaxVolSets
This determines the maximum number of IndexVolumeSets to search simultaneously.
Format :-     FederatedSearchMaxVolSets=# where # is a number.
Default :-     5 (if not set).
·         FederatedSearchMaxItems
In order to control how IndexVolumeSet results are merged together there is IndexVolumeSet. That number is this property a limit to the number of items that should be obtained from each, MaxVolSetsItems.
Consequently this number also determines the maximum number of results that a user would see matching his query. This is because it is possible that the most relevant results, after sorting etc. for his query came from ONLY one IndexVolumeSet.
Format :-     FederatedSearchMaxItems=# where # is a number.
Default :-     1000 (if not set).
·         FederatedSearchTimeout
This is a time limit to determine how long the federated search can take before it should be ended.
Format :-     FederatedSearchTimeout=# where # is a number of seconds.
Default :-     60 (if not set).
·         UseFederatedSearch      
This controls whether “federated searching” should be allowed for everyone who uses the WebApps. It maybe the administrator wants to turn off this functionality perhaps for configuration / performance reasons.
Format :-     UseFederatedSearch=# where # is a number.
Default:-      1 (if not set).

EV Backline Technical Support Engineer APJ Region