Content Consistency Checker Overview

Content Engine provides a Content Consistency Checker that synchronizes the object store database with file storage area content.

The Content Consistency Checker detects inconsistencies between the metadata in the object store database and files in associated storage areas.

NOTE  This procedure is not necessary when backing up or restoring your object store database if you store the content with the metadata in the database. If you manage your database backups and restores using the tools provided with the database itself, its data is always in-sync with the object store.

When to use the Content Consistency Checker

You should use the Content Consistency Checker under any of these conditions.

Selecting documents to check

With the Content Consistency Checker, you can check content stored in the file system. You can select one or more file storage areas within a specific object store.

Security requirements

To run the Content Consistency Checker, you need permissions to read the file storage area you want to check. You do not need read permissions for the documents stored in the file store.

By default, object store administrators have access to all objects in the system, enabling them to perform the check. If you change the default security settings, you can affect who has permissions to run the Content Consistency Checker.

Error detection

The Content Consistency Checker detects the following major error types:

File does not exist
This error indicates one of two conditions:
File is not the right size
The file size is never wrong under normal conditions. This error indicates that either the object store or the storage area contains the wrong size for the file. The incorrect size can result if, for example, the file in the storage area is either an old version or has been overwritten by another file. Examine the document content and restore the proper file if possible.

For details on other error types, see Validation Errors.