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 Recovery

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

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

• Network connections to the filerserver fileserver may be very slow

• There is content such as a large number of many logs, csvCSV, and large excel 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.