Possible impact. Since GEODI works with big data, some rules in security tools during communications may slow operations or completely prevent communication. In such cases, the relevant GEODI tools should be excluded from these rules with the support of the DECE technical team.

This is normal behavior. Power outages, system hardware problems, deliberate application shutdowns, and many other issues can cause unintentional shutdowns. In this case, the index will undergo a health check at the next startup for possible damage, and any errors found will be fixed.

To speed up the process, you need to back up the index and recover from backup on startup. Recovering from backup does not cause irreversible data loss. The next time you index what has changed, the latest additions are refreshed.

Active-Passive and Active-Active configuration

Index Backup and Recoveryarchived

GEODI is designed to make optimum use of the server. Server memory and CPU resources are used dynamically. The number of concurrent tasks is increased for simple and fast processing files and decreased for heavy files.

If the processing is too slow

• Memory may be low or being used by other processes running on the server

• Some processes may consume high CPU resources, such as intensive OCR.

• Network connections to the fileserver may be very slow

• There is content such as many logs, CSV, and large Excel files.

• There may be network problems with database connectivity or database congestion.

• The GEODI indexing speed mentioned in the Project Wizard may be the lowest.

Periodic backup of the index and creation of an active/passive DRM environment is described on page Active-Passive and Active-Active configuration By only backing up, it speeds up the system startup and activation in case of possible interruptions.

In the Advanced settings on the last page of the GEODI Project Wizard, the project index backup directory can be given against possible system outages. GEODI index can be used through this directory in case of possible interruptions. You can use the Index Backup and Recoveryarchived page for backup.

GEODI indexes only the name of password protected files. Protected files indexed in this way can be listed with the queries "status:GEODICryptedContent" or "status:GEODICryptedContentPart".

Files with errors can be queried with “status:HasScanError”

This behaviour is by design. In order to remove deleted files from the GEODI index, you need to delete deleted files from the Project Management interface.

Windows can access directories up to 260 characters long.After this value, “System.io Path too Long Exception“ error is received. As a solution, you can edit the path appropriately (mapping).

GEODI keeps its logs under appdata/dece/logs These logs are in CEF format and can be processed by SIEM tools.

%AppData%\Dece\Logs\GEODI\AppUsage directory contains the logs required for SIEM.

In case you mention another friend in the notes, tracking query is forwarded to the email. There may be a problem with the settings made on the server for this purpose. You can access through GEODI Management Panel / settings.

If the problem occurs in a number of users, Spam folders or mail rules should be checked.

GEODI checks for an update on startup and if you confirm, an update can take place. The index structure may be converted to the new version according to the features introduced in the new version. This is indicated by a warning. It is recommended to back up the old index before proceeding. GEODI must be turned off during the update.