Topics | How To |Related Topics
Applying Updates for the Content Indexing Engine
Content Indexing Options for Jobs on a Storage Policy
Operations performed with this feature are recorded in the Audit Trail. See Audit Trail for more information.
The following Alerts can be generated if configured:
See Alerts and Monitoring for more information.
The Space Check feature monitors consumed space and free space remaining in the computer in which the Content Indexing Engine is installed. An event is generated in the Event Viewer when limited space and consumed space are detected in the computer in which the Content Indexing Engine. A Disk Space Low alert, if configured, will be generated if the disk space falls below the defined threshold.
See Space Check for more information.
The following alerts can be generated, if alerts are configured:
See Alerts and Monitoring for more information.
|
It is recommended that the <DISK SPACE INFO> token be included in the notification message if configuring a Client alert with Disk Space Low criteria. This will provide detailed information including when and where the low disk space was detected. |
Consider the following for applying updates in computers with the Content Indexing Engine software:
Both the Online and Offline Content Indexing jobs are restartable. See Job Preemption Control for more information. If necessary, you can specify the maximum number of allowed restart attempts and the interval between restart attempts. See Specify Job Restartability for the CommCell.
You can also set the Job Retries and Job Running Time options when initiating a job. See Restarting Jobs and Job Running Time for more information. See Start or Schedule Offline Content Indexing Operations and Start or Schedule Online Content Indexing Operations for step-by-step instructions.
When you prune data based on data retention rules, the corresponding content index for the data also gets pruned from the content indexing engine. For more information on pruning data using data retention rules, see Data Aging. However, if there are multiple copies of the data and you are pruning the data in only one of the copies, then the content index for that data does not get pruned automatically. Use nDocumentAgingPeriodInDays key to manage the frequency of pruning of Tagged data in the database.
Also, if for some reason, you need to prune the content index before pruning the data, you can do so using the retention rules available in the Storage Policy Properties (Content Indexing) tab. For step-by-step instructions on setting the retention rules for pruning content indexes, see Configure Retention Criteria for the Content Index.
Note that, when you disable content indexing for a storage policy, a warning message is displayed prompting you to whether de-configure and remove all the content indexes associated with this policy. On selecting Yes, all the content indexes associated with the specific storage policy gets pruned and the content indexing feature is disabled. On selecting No, the content indexes are retained, but the content indexing feature will be disabled for the storage policy.
When you migrate a client from one CommCell to another, all the protected/archive data associated with that client needs to be re-content indexed. For more information on content indexing protected/archive data, see Offline Content Indexing.
Also, if you are migrating a client with Online Content Indexing agent, you need to uninstall the Online Content Indexing agent and re-install it in the new CommCell.
Similarly, when you are manually starting the content indexing services, make sure that you start the services in the admin node first and then the start the services in all the index/storage nodes. For step-by-step instructions on starting the services, see Start Content Indexing Services.
If you need to reboot the admin node, make sure that you stop the services in all the nodes first and then reboot the admin node.
You can use the following content indexing options for jobs on a storage policy :
This option allows you to select a job for content indexing. Once selected, the Content Index Status field for the specific job will be changed to Picked (i.e., the next content indexing operation will include this job for content indexing). For step-by-step instructions on selecting a job for content indexing, see Select/Prevent Content Indexing for a Job on a Storage Policy.
This option allows you to prevent a job from being content indexed. You can apply this option to those jobs that were previously selected for content indexing. On selecting this option, the Content Index Status field for the specific job will be changed to Not Picked (i.e., the next content indexing operation will not include this job for content indexing). For step-by-step instructions on preventing a job for content indexing, see Select/Prevent Content Indexing for a Job on a Storage Policy.
This option allows you to re-select a job for content indexing. You can apply this option only to those jobs that were previously content indexed (i.e., when the Content Index Status is Success). On selecting this option, the Content Index Status field for the specific job will be changed to Picked (i.e., the next content indexing operation will include this job for content indexing). For step-by-step instructions on selecting a job for content indexing, see Select/Prevent Content Indexing for a Job on a Storage Policy.
In order to re-pick multiple jobs, you need to first delete the content index of the selected jobs and then pick the jobs for content indexing.
Similarly, if you want to re-pick a partially content indexed job (with content index status partial) for content indexing, you need to first prevent content indexing for the job and then pick the job for content indexing.
This option allows you to delete the content indexes for a job that was previously content indexed and also prevents the job from being content indexed further. Once deleted, the Content Index Status for the specific job will be changed to Not Picked (i.e., the next content indexing operation will not include this job for content indexing). For step-by-step instructions on deleting the content indexes for a job on a storage policy, see Delete Content Indexes for a Job on a Storage Policy.