Topics | Support
Overview of Content Indexing and Search
Content Indexing and Search Components
Content Indexing and Search consists of the following main components. The diagram on the right provides a broad overview of the deployment and configuration of these components. Content Indexing EngineThe Content Indexing Engine is the core component for the content indexing and search feature. It is the underlying integrated software application that provides indexing, searching and filtering services for all data - including file server/desktop data and protected/archived data. As the content indexing process is very resource intensive it is recommended that the engine be installed in powerful computer that has extensive memory and hard disk availability at all times. (See System Requirements - Content Indexing Engine for minimum requirements.) The Content Indexing Engine may be installed as a single-node installation where all the components within the Content Indexing Engine are installed in the same computer. Depending on the volume of data that must be content indexed in a CommCell, one or more Content Indexing Engines can be installed and configured. You can also perform a multi-node install to customize the installation of each Content indexing Engine to distribute and harness the capacity of multiple computers. Content Indexing Engine is the first component that must be installed. (See Deployment - Content Indexing and Search for more information on how to install the Content Indexing Engine.) The properties of each Content Indexing Engine in the CommCell is displayed in the CommCell Console under Storage Resources. Once installed, you can configure the content indexing engine to set the maximum number of batch slots and maximum number of documents per batch. You can also specify a staging location where the files to be content indexed will be staged temporarily prior to content indexing. Both offline and online content indexing processes are configured to use a Content Indexing Engine. This is explained in the following sections. Offline Content IndexingOffline Content Indexing is used to content index the storage data secured by the various data protection/data archive operations. For this reason the configuration of the Offline Content Indexing is associated with a storage policy. Each storage policy must be configured to use a Content Indexing Engine, if content indexing is enabled in the storage policy. (See Configuration - Content indexing and Search for more details.) The MediaAgent associated with the Storage Policy will be used for reading the data associated with the storage policy. Offline content indexing is supported for all types of of data including compressed, deduplicated and encrypted data. Offline Content Indexing for RMS Protected DocumentsYou can also perform offline content indexing of documents/emails secured by Rights Management Service (RMS). Rights Management Service (RMS) is a technology that works with RMS enabled applications (such as, Microsoft Office applications, Microsoft Exchange Server, and Microsoft Sharepoint Server) to set usage rights on documents or emails. This is basically used by content authors to set permissions on their documents/emails in order to limit access to other users. For more information on Rights Management Service, refer Microsoft documentation. For more information on content indexing RMS protected content, see Content Indexing RMS Protected Files. Offline Content Indexing for NAS AgentsOffline content indexing is also supported for NAS backups. See Content Indexing- Support for a list of data types that are supported by offline content indexing. In order to view or restore the content indexed NAS data from the Search Console, install the Deployment - File System NDMP Restore Enabler on the web search server.Offline Content Indexing for Virtual Server iDataAgentOffline content indexing is also supported for file level backups on VMware virtual servers. See Content Indexing- Support to know the virtual server platforms supported by offline content indexing. Offline Content Indexing for Lotus Notes/Domino ServerOffline content indexing is also supported for Lotus Notes email backups. In order to enable Domino Directory Service login or to restore Lotus Notes emails, you need to install the Lotus Notes Client on the Web Search Server on a 32-bit platform. Online Content IndexingOnline Content Indexing operations can be performed using the following agents: Online Content Indexing for File System AgentThe Online Content Indexing for File System Agent allows you to content index live files residing on Windows computers. The Online Content Indexing Agents must be installed on all the computers in the CommCell that you wish to content index and search. See Deployment - Content Indexing and Search for information on installing the Online Content Indexing agents. See Configuration - Content indexing and Search for information on configuring the Online Content Indexing agents. SearchOnce the data is content indexed, it can be searched for data discovery and other purposes. Search can be performed using the following components: Web-based Search ConsoleThe web-based Search Console provides a multi-purpose and flexible method to search and if necessary restore data. It has an easy-to-use search interface modeled after popular search engines. In order to perform searches from the Search Console, you need to install the Web Search Server and the Web Search Client. For information on installing the Web Search Server and Web Search Client, see Deployment - Content Indexing and Search. In order to view or restore the content indexed NAS data from the Search Console, install the Deployment - File System NDMP Restore Enabler on the web search server.Once installed, the web-based Search Console and User security must be configured before it is used. See Configuration - Content indexing and Search for more information. The Search Console also has powerful built-in security features that enables both compliance and end-users to search data based on individual security permissions. In addition, it also allows users to restore the appropriate file/data if necessary. The Search Console provides several options and tools to search the data. It also provides following additional advanced search options to further refine your search.
During search, you have the facility to include intra operators against search criteria in the advanced search options window. It also allows users to preview the search results in the same or new window. When performing end-user search, the Search Console also provides options to search for Exchange emails on delegated mailboxes for a specific user. This is described in Data Discovery and Search. Domino Directory Services Login Lotus Notes Domino users can now login to the Search Console as end-users using Domino Directory Services. In order to enable Domino Directory Service login or to restore Lotus Notes emails, you need to install the Lotus Notes Client on the Web Search Server on a 32-bit platform. You also require to add a new domain controller for Domino Directory Services. For detailed information on adding a domain controller for Domino Directory Services, see Add a New Domain Controller for Domino Directory Services. If Active Directory end-users need to search for Lotus Notes emails, they can do so by authenticating with the Domino domain server. User Administration The User Administration page is used to configure user preferences for end-users and compliance users when performing searches from the Search Console. It also provides facility to upload customized logos to the Search Console. In addition, you can also view the analysis of searches performed on the Content Indexing Engine for a given time range, using the Search Analytics tool. For detailed information on configuring user preferences from the User Administration page, see Configuration - Content indexing and Search. Legal HoldLegal Hold provides the ability for a compliance user to segregate relevant information found during a data discovery and search operation and preserve them for long term retention for legal purposes. It uses a policy based approach to search relevant data and retain a subset of the data for a long retention period. Legal Holds can be created from the Search Console as well as the CommCell Console.
TaggingWhen performing search on content indexed data, you can assign tags to the discovered items for easy identification/classification. These tagged items can then be searched based on the tags. There are pre-defined tags or system tags already available in the CommServe. In addition, you can also create user-defined tags from the CommCell Console. Tagging is applicable only for Compliance users and administrators.
For detailed information on creating and assigning tags, see Tagging. ERM ConnectorsERM (Enterprise Records Management) Connectors allows you to submit discovered documents and files to a record management system. Currently, the software supports submission of documents to Microsoft SharePoint Record Center. When you create an ERM Connector, you pre-define the mapping of documents to a specific ERM server in the record management site. ERM Connectors can be used only by Compliance users. You can create and use ERM Connectors from the Search Console as well as the CommCell Console.
For detailed information on using ERM Connectors, see Enterprise Records Management (ERM). Content Director PolicyThe Content Director Policy is a component under Content Director node in the CommCell Console, that allows you to automate and schedule the data discovery and search operations, such as Legal Hold, Tagging, Restore to Review Set, and ERM Connector. You can also use the policy to restore the discovered items to a review set in the Web Search Client. When automating these operations, you can also specify the date from which the backup/archive data will be considered for the search. If a particular job is qualified to be processed by the Content Director Policy, it will be not be pruned even though eligible to be pruned, until acted upon by the policy. For more information, see Content Director Policy. |
This feature requires a Feature License to be available in the CommServe® Server.
Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.
The Content Indexing and Search package requires the following licenses:
Security plays a key role in searching data. Security for search operations is handled using the Active Directory (AD) security which ensures that the logged in user will only be able to access the files/data that were created by the specific user. (Default read access on files is dictated by the operating System's Type and Security settings.)
However, note that UNIX and NAS data is accessible only to the Compliance user. For more information on security settings for data search, see Security.
For information on security settings for Legal hold, see Security Considerations.
For information on the security settings for Tagging, see Security Considerations.
For information on security settings for Records Management using ERM Connectors, see Security Considerations.