Configuring Indexing for Gmail
NetGovern eDiscovery can include data in an external Gmail location. To set up the Indexing and Archiving jobs required to make Gmail content available and searchable in NetGovern eDiscovery, you must have configured the Gmail connector—see Configuring Gmail Connector.
When the connection to Gmail has been configured and a Gmail Archive Storage location or Email (Gmail) Live Location has been created in the NetGovern Admin UI, Gmail can be selected as the source location for Indexing and Archiving jobs.
The Gmail Index job must be set up and run in order to search archive data in Gmail. When the Gmail Index job is configured, messages will be indexed according to the criteria and schedule set.
Indexing and Archiving jobs must be configured in order to make the Gmail content available in NetGovern .
Indexing is performed to make the data searchable. If you intend to search the archive data, the Gmail Index job must be set up and run prior to the Gmail Archive job—see Configuring Gmail Archiving.
It is not necessary to create a policy in NetGovern to guide this job.
- Select Archiving > Agents > Email Indexing.
- At the bottom-left of the License tab, click Create.
- Select Gmail from the Source Type drop-down menu.
- Give the job a meaningful name and click Create.
- The new job is created and appears under Email Indexing. Click on it.
- Open the Criteria tab.
- Navigate to the Source section. In the Crawler field, use Find to identify the Gmail Storage or Live Gmail Location you previously created—see Configuring Gmail Connector.
- You can enable Incremental Indexing to ensure data is indexed based on the account check point stored on the mail box.
- In the Policy section, you can enable Filter by query. Selecting this option will allow you to enter a policy query in the field below.
- Click Save.
- Open the Job Settings tab.
- Enter a meaningful Description. You can enter the name of the index job.
- Set the appropriate Job Priority. You can choose between Low, Normal, and High. By default, the Priority is Normal.
- Set the appropriate Mode:
- Continuous: Indexes operate on a continual basis without interruption. The index keeps up to date with all changes in the location.
- Pause: Stops indexing. Once the initial index is built, there is no need to continue running it.
- Pause and delete indexes: Stops indexing and deletes the existing index.
Then, it re-indexes once, and pauses.
- Click Save.
- Logging provides you with detailed job logs that can assist with job troubleshooting, if needed. In the Log Settings tab, configure the desired log settings:
- Disable Detailed Logging (Default): Deactivates logging.
- Enable Logging: Activates logging for troubleshooting purposes.
- Enable Logging Only for the Next Run: Activates logging the next time the job is run, and then automatically returns logging to ‘disabled’ state.
- You can also have email Notifications sent at the completion of the Gmail Index job, along with attachment options.
- For further information on logging—see Configuring Logging.
- Click Save.
- (Optional) In the Report tab, check on the progress of the Gmail Index job.
For further information on reports—see Viewing Reports.
- To archive the Gmail data and search the archived Gmail content—see Configuring Gmail Archiving.
This setting is useful in scenarios where multiple jobs are running concurrently and you want to control which job takes priority with respect to thread allocation. The job priority you select determines which job in the queue is selected next by the Job Manager process, which is responsible for allocating queued job threads to available thread slots on the archive nodes. Prioritization is categorized according to user account. For example, you may want to assign higher priority to crawling files created by VIP users. If a normal priority job is already running and using all available job threads, setting the priority to high and executing it will direct any freed threads to be used on the new high-priority job. This feature works in conjunction with load balancing in order to control crawling job distribution.