Versions Compared

Version Old Version 11 New Version Current
Changes made by

serdar ak

serdar ak

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Indexing is what GEODI crawls all data and runs the the result of discovery. GEODI creates brief information about the data and uses this brief to answer searches, reports, and all others. GEODI will not need the original data unless you want to open it in a viewer or start indexing.

Table of Contents
stylenone

...

Info

Indexing Speed

  1. GEODI has an indexing speed settings. We suggest that you set it to maximum. Please check the details on Settings page.

  2. There are other factor that affects indexing speed:

    1. The time very depends on the CPU, memory, Memorydisk, Disk and other server resources of the Server that GEODI runs on.

    2. Data throughput of the Network and Disk of data sources are also very important.

    3. Options like OCR or FacePro greatly affect the performance.

...

Info

Options

The beginning should be “Index all Content”. After thathat, you may use all other options. If you set scheduled indexing and have periodic backups you will not need to use options other than maintenance needs.

...

Info

Monitoring Indexing

Once you start indexing, the process can be monitored.

  1. The progress bar shows the aprozimate percentge approximate percentage of indexing. Please be careful about the progress bar, which is not lineerlinear. That is GEODI can an not know how much time it will require to index for future documents, so the progress bar is only an estimate using the previous document indexing time.

  2. This area shows the numbers. The gr graphics shows trend show trends in terms of document/second.

  3. This are shows if any error or warning was generated. You can ca click and download the report. This report resides in %appdata%logs folders. This link downloads a detailed log about indexing named timelog. Timelogs can also be foun in %appdata%\logs , which resides in the % appdata%logs folder.

  4. Error reports and detailed reports about the project.

image-20240920-105836.pngImage Removedimage-20240921-092936.pngImage Added

Info

Index Storage

  1. The index needs some storage. The size si e will be much smaller than the data, but it is unpredictable. You may ma assume %10 to %20 generally.

  2. Options like sampling mode or similarity indexing., affect the index size.

  3. A backup space for the index should also be reserved for uninterrupted service.

Info

Continuous Discovery

Once you index data sources, the process will repeat automatically for new data(rows, files, emails, etc.). You do not need to intervene; just tell GEODI the recheck period. This is i done in Project Wizard.

Sampling

Sampling is possible for both , structured and unstructured data. Each data d ta source asks you for the sampling values. Sampling saves great time for discovery projects. We suggest sug est you always use sampling for DB discovery. For unstructured data, sampling is also a good starting point. Start with ith sampled mode and see what is in the data, whether there are there any unnecessary types, or are whether there is any permission problem.

Filecontent Filtering

Any corpus contains various file types. Some may not be necessary for the project scope, and some may be too large to disrupt for the network or unwanted at allthe system.

GEODI comes ready with default rules to avoid some file types and place some size limitations, collected from the best practices of many Discovery projects. Here, we e documented the rules and how you can modify them.

These filters apply to all files, whether they come from a folder, from an email attachment, from GDE, or embedded into a database.

Filters (%100)

Explanation

IgnoreRules

Ignore rules contain file extensions, directory names and some patterns.

Default list contains *.DLL, *.SYS, “programm files” and similar.

Any file matches ignore rules are not indexed and logged at all.

Settings are in:

  • <geodi>Settings\IgnoreFileTypes

  • <geodi>\Settings\IgnoreFolders

(warning) If you need to override defauls please do it in %appdata%

(info) GDE has some additional ignorerules documented in the related page.

KnownFiles

These files are the ones GEODI has a reader like PDF, DOCX etc. The full fu l list is Supported Formats

These files are processed as expected unless there is an IgnoreRule or ProtectRule. Ignorule will set the file type invisible. Protectrule Protec rule may set so size limitation.

UnknownFiles

By default unknownfile types are ignored.

You may override this settings from Project Wizard advanced settings.

If you use “only name and date” then all unknown extensions will be indexed.

You may add any unwanted to ignore list but these actions requires to run discovery all over again.

image-20240919-115040.png

ProtectRules

These rules is to protects system and network again too large files. Protect Protec rules apply to known and unknown files.

The content are grouped as local and far. There is s no limitation for local content which resides in local folders and network folders. Far means me ns files from GDE, e-mail email attachments and files from web pages.

By default, Far content is filtered as any file greater than 100Mb, and Compressed files greater than 500Mb are indexed as name only. You will wi l know these files but not their content.

Settings are in:

<geodi>\Settings\Engine\ResourceBalancing

(warning) If you need to override defauls please do it in %appdata%

...

  1. status:OnlyName → gives the content with only nane and date. These files iles comes from UnkownFiles and ProtectRules.

  2. status:HasScanError → Files unread by file error, encyiption or so. These files iles are marked by an ! at the name.  

  3. status:IsContainer → Files within a folder or ZIP/RAR.

  4. status:IsCompletedIndex → Content succesful indexed.

  5. status:Crashed → Incase of an index recovery after a system crash GEODI will recover the index. This query q ery shows the unsuccesslful content. To avoid avo d these you should use index backup.

  6. Status:PartialRead → Content partialread by protectRules.

  7. GEODICryptedContent → encyripted content. 

  8. GEODICryptedContentPart → parlt encyripted content

...

Expand
titleIndexing is slow

GEODI discovery engine is one of the fastest among other discovery engines. Slow indexing i dexing may depend on machine, settings or enviroment.

  1. Check indexing speed and be sure that speed is high

  2. Check engine errors, If a source is throwing too many errors this may slow down the indexing

  3. Another task may be using too much resources,

  4. Too many recognizers may slow down a indexing

  5. Slow disk may slow down indexing. Consider Consid r dividing index and putting some part to a fast disk, like SSD.

  6. Use sampling mode if you need a quciker result

Expand
titleToo much CPU is used

High CPU usage for an engine like GEODI should be expected. CPU usage of GEODI never goes to an unresponsive machine state. GEODI always leaves one core to other tasks.

  1. CPU usage may be temporary, just wait to see if it drops

  2. If a consistent CPU usage try decreasing indexing speed

  3. OCR or FacePro needs CPU, if you are using these options, decrease indexing speed or wait.

Expand
titleIndex size is too high

GEODI compressed to index as much as possible. Index size upto %20 up % to 20 percent of corpus size should be expected. If it looks too high to you, then you may try the following.

  1. Similarity index may be open. This index need dex needs the disk.

  2. Some files may hav too much information (logs, csv etc), you may exlude them.

Expand
titleIndex errors

GEODI generates error logs during indexing. These logs mostly are about concern content and shuld should be considered as warning warnings or infoinformation. There may be real erros about system , errors; you will be informed about them.

Most of them are

  1. Unreadable content

  2. Encyrpted content

  3. Unreachable content (because of permissions)

...

Expand
titleMyDocument count and GEODI content count does not match

The GEODI content count includes all folders and files in compressed files like ZIP and RAR, RAR. So it is normal so it's normal for the count not to match.

And some filetypes may be in ignorelists.

Other than that be sure that GEODI covers all.