Searching with a Discovery Team

A Discovery Team is composed of managed endpoints that have been grouped together for the purpose of automatically assigning the work of a search. A Discovery Team can be used in a many-to-many scenario where a designated group of endpoints is tasked with searching managed and unmanaged endpoints and remote locations. A team can also be used in a many-to-one scenario where a group of endpoints can divide the work of searching a large data store. Depending on the configuration of the settings, team members can work individually or cooperatively, as detailed below. Please refer to the Discovery Teams topic in this user guide for the creation and configuration of Discovery Teams.

Discovery Team searches are available when using Scheduled Task Policies. To configure a search using a Discovery Team, select the Policies tab, then select a Scheduled Task Policy from the Policy list and click on Scheduled Tasks. Add a new scheduled task or edit an existing one, select Search using this Discovery Team and select a Discovery Team from the drop-down.

Clicking the Perform distributed searching with load balancing Manage button opens the Discovery Team Search Settings dialog:

There are three options available for searching with a discovery team, Perform distributed searching using all available team members, Load balancing, Override default minimum (2 GB) and maximum (20000 GB) Loads, Override default minimum (20000) and maximum (100000) number of items and Reassign load if Team Member is unresponsive for x minutes.

Depending on the configuration of the Perform distributed searching using all available team members and Load balancing settings and whether there is a single target or multiple targets to search, the search performs differently, as described below.

Single target

When searching a single target, Discovery Teams provide the ability to distribute the load across multiple team members and therefore significantly reduce the total time needed to search the target.

The text on the Scheduled Task page reflects the selections you have made in the Discovery Team Search Settings dialog as follows:

The Reassign load if Team Member is unresponsive for x minutes setting determines when to reassign a data set from an unresponsive team member.

When the Console does not receive an update from a Discovery Team member after the specified period of time, the data set that was assigned to that team member is reassigned to the next available team member. The default value is 1,800 minutes. Valid values are 1-999,999.

 

Note: If the Scheduled Task policy is configured to search using a Discovery Team, specify the target system(s) to search by checking the box next to each desired tag or endpoint on the Endpoints page of the policy. If no endpoints are selected, target path(s) must be specified as Custom Folders or as Remote Machines.

Note: Once the analysis of the targets to be searched has completed, the actual searching of the targets may not begin immediately. The analysis must first be processed and team members must be assigned a data set to search so there could be a short delay before searching begins.

Note: Load balancing is not utilized for the searching of Websites as there is no way to determine the size of each location of those types. What happens is that a single team member is selected to search an entire Website. For example, if you have three websites defined in your policy, each website to be searched is assigned to a single machine and the load is not distributed across multiple team members.

Note: Load balancing can be utilized for the searching of Exchange Servers and Databases providing the Console is at version 10.0.2 or higher and the Endpoints are at version 10.0 or higher. Databases cannot be split if the total data in the Database is smaller than the Minimum load when using load balancing setting on the Applications Setting page. Databases are split by table. Exchange Servers are split by folder.

Note: Search History may not be relied upon for Discovery Team searches due to the fact that it may be a different team member performing the search of a specific data set on subsequent searches. In order for Search History to work properly, the same endpoint must perform the search of the same data on each subsequent search.

Note: Live mode, which checks the previous results for existence on the next search, is forcibly disabled in Spirion version 9 for Discovery Team searches. It is not forcibly disabled in version 10 however, it may not be relied upon for Discovery Team searches due to the fact that it may be a different team member performing the search of a specific data set on subsequent searches. In order for Live mode to work properly, the same endpoint must perform the search of a data set on each subsequent search.

Additional Information

Please refer to the Scheduled Tasks user guide to configure a search using a Discovery Team.