Use this dialog box to enable and configure content indexing for the selected storage policy.
Enable Content Indexing
Specifies whether Content Indexing is enabled or not. When enabled all the other options for Content Indexing are enabled. The options are provided in the following tabs:
Content Indexing Engines
Displays the name of the Content Indexing Engine that will be used by the storage policy. To select, click one from the list.
Selection Rule
When selected, all backups to this storage policy (including the primary and all copies) will be content indexed.
When selected, you can customize the selection of data to be content indexed from the Selection Rule dialog box which appears when you click the Advanced button.
Click to define customize the rules that must be used to select the data for content indexing.
Subclient Association
When selected, indicates that data from the specified subclients will be content indexed.
When cleared, data from all subclients that use this storage policy will be content indexed.
Click to display the Subclient Association dialog box which allows you to add or remove subclients for which data must be content indexed.
Source Copy
When selected, you can specify the name of the copy that must be content indexed.
When cleared, the software will use a storage policy copy pointing to a disk library and/or use the storage policy copy with the lowest copy precedence.
Defer Content Indexing for x day(s)
When selected, specifies that data can be content indexed only after an n amount of days after the data was protected.
Backups On and After
When selected, specifies a backup on and after the specified date will be used for content indexing.
By default the system content indexes all the file/MIME types listed in Supported Document Formats. (This list also provides a list file/MIME types that can be included or excluded from being content indexed.)
Include Global Filters
Specifies whether global filters for offline content indexing will be included or not. Set the value to either ON or OFF.
Include following file types for Content Indexing
Specifies that the file types listed in the box (displayed below) will be content indexed.
Exclude following file types from Content Indexing
Specifies that the file types listed in the box (displayed below) will be not be content indexed.
Remove from list
Highlight the file type from the file types listed in the box, and click this button to remove it from the list.
Add new file extension
When selected, allows you to add additional file types to the file types list.
File Extension
Use the box, to enter a new file type.
Add
Click to add the File Extensions that was added to the file types list.
File Size
Specifies the minimum size of the files that will be content indexed. File sizes which are below the specified size will be skipped.
Specifies the maximum size of the files that will be content indexed. File sizes which are above the specified size will be skipped.
Note that the content indexing engine can process files sizes of up to 50 MB. Files which are over 50 MB will be automatically skipped.
Retention rules for Content index
When selected, specifies that the retention for the content index is based on the retention rule established for the associated data in the storage policy copy. The content index will be automatically deleted when the associated data is aged.
When selected, the content index for each backup job will get pruned after n number of days from the start of the backup job. However, 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.
For example, if you specify to retain the index for 360 days and if the retention for the backup job is set as 180 days, then the index will get pruned along with the backed up data after 180 days.
Sets the retention rule on the content index based on the pending content director policy operations.
When selected, the search results cannot be previewed from the Search Console as well as the CommCell Console.
When selected, synthetic full jobs will not be content indexed.