Automatic data consistency check and fix in Kerio Connect

This topic describes possible options and steps available in Kerio Connect to do message store consistency check.

Kerio Connect automatically walks through data storage on background and performs check of auxiliary files and fix in case of detected corruption. It is possible to run fix of corrupted data directly from web administration for specific users or for public folders.

For the user folder

1. Log into the Kerio Connect Administration with a user account that has read/write rights within the Administration.
2. Within the Administration, go to Accounts > Users
3. Select one or more users and right-click. Select More Actions… > Reindex Mailbox

For Public folders

1. Log into the Kerio Connect Administration.
2. Within the Administration, go to Configuration > Domains
3. Click on the Public Folders… button and press Reindex Folders

Schedule of automatic storage check

• Complete check of all folders on the server

• Immediately after startup (starts in first 30 seconds)
• Every 6 hours

• Fix of corrupted properties.fld files, which contains extended messages attributes.

• 1 hour after startup
• Every 7 days

Beside of periodic check, corruption can be also detected during user’s access to folder, in that case is folder added to automatic check queue and almost immediately is checked and fixed. Corrupted calendar and contact folders are processed with higher priority.

Check on each folder consists of the following steps:

• Check the file with information about folder status.fld, and in case of file corruption, default values of missing attributes are used.

• If status.fld doesn’t exist and folder is not one of standard folders (Inbox, Calendar, Contacts, etc.), folder is not valid and is not listed in client applications.

• Check the file with information about messages index.fld

• If any corruption is detected or if file is not found, index is reconstructed from messages physically stored in folder #msgs.
• If the index is valid, but it’s records doesn’t correspond to physical messages on the disk (in folder #msgs), redundant records are removed from index and missing messages are supplemented.

• Check consistency of file search.fld, which is used to search in messages.

• If corruption is detected, the file is removed and completely reconstructed.

• Detection of invalid name of messages, used by WebDAVWeb Distributed Authoring and Versioning is a framework that enables users to work with documents on a server. protocol (called DAV-names) and fix of the names.

As part of automatic control following additional actions are performed:

• Old messages are deleted, according to appropriate server settings – i.e. feature Items Clean-out and Deleted Items Recovery in domain settings.
• Check and fix of folder #deleted, in which are archived deleted messages, which can be restored by feature Recover Deleted Items.
• Check database of shared folders, which is used in CalDAVCalendaring extension to WebDAV that enables you to synchronize calendars. protocol, i.e. file .caldav.db.
• If more folders with the same GUID identification are detected, identification of one folder is automatically changed by newly generated.
• Fix of corrupted UIDs of calendar events.