The following Alert can be generated if configured:
Offline Content Indexing - Use the
Offline Content
Indexing alert to generate alerts for monitoring offline content
indexing jobs.
Online Content Indexing - Use the
Data Protection alert to
generate alerts for monitoring online content indexing jobs. Note that only
the job related options (Job Succeeded, Job Skipped, Job Failed, and Job
Activity) are applicable when generating an alert for online content
indexing jobs.
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.
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:
Updates for the Content Indexing Engine can be installed interactively -
Automatic Update are not supported. Use the following sequence to install
the updates on these computers:
Verify that no Content Indexing jobs are in progress or scheduled to
occur while installing the updates. If Content Indexing jobs are
running or scheduled to run, either install the update at another time or
kill the job in the Job Controller and disable all Content Indexing jobs
from the CommServe Properties (Activity Control) dialog box in the
CommCell Console.
First, stop the Content Indexing Services in all the Index/Storage Nodes
and then stop the services in the Admin Node.
Follow the below procedure
to stop the services:
Log on to the computer containing the Content
Indexing Engine software.
Click Start menu, and then click Run.
Type services.msc in the text field and press
enter.
From the services.msc console, Right-click the FAST ESP service, and
then click Stop.
Install the necessary Updates.
First, start the Content Indexing Services in the Admin Node, and then
start the services in all the Index/Storage Nodes.
Follow the below
procedure to start the services:
Log on to the computer containing the Content
Indexing Engine software.
Click Start menu, and then click Run.
Type services.msc in the text field and press enter.
From the services.msc console, Right-click the FAST ESP service,
and click Start.
Enable Activity Control if it was disabled and re-run the job if
necessary.
When installing updates, make sure that all nodes in a multi-node setup have the
same set of updates - mismatches in the updates should be avoided
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.
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.
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.
By default, the content indexes get pruned along with the data based on the
data retention rules. Use the following steps if you want to retain the content
indexes for a specific number of days and prune it before pruning the data.
From the CommCell Browser, navigate to Policies | Storage
Policies.
Right-click the <Storage Policy> and
select Properties.
Click the Content Indexing tab.
Click the Retention tab.
Select Retain for n Days and specify the number of
days until which the content index will be retained from the start
of the backup job.
Note that if the specified
number of days is greater than the retention days set for the backup job,
then the index will get pruned along with the backed up data.
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.
Once you have installed the Content Indexing Engine, the Content Indexing
Services get started automatically. In a multi-node setup, when you need to
manually stop the services, make sure that you stop the services in all the
index/storage nodes first and then finally stop the services in the admin node.
For step-by-step instructions on stopping the services, see
Stop Content
Indexing Services.
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 :
Pick for Content Indexing
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.
Prevent Content Index
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.
Re-Pick for Content Index
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.
Delete Content Index
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.
