DocumentationExperience Cloud KCS

AEM LTS upgrade: Offline datastore and index consistency check recommendations

Last update: October 26, 2026

✨ This content is AI generated and could be inaccurate. Generative AI Terms

This article explains if offline datastore and index consistency checks are necessary as part of the pre-upgrade steps for Adobe Experience Manager Long-Term Support (LTS) upgrades.

Description description

Environment

  • Adobe Experience Manager (AEM) 6.5 LTS (all platforms)
  • Applies to both TarMK and MongoMK deployments

Symptoms

When preparing for an AEM LTS upgrade, questions may arise about whether offline datastore consistency checks and index consistency checks are required as part of the pre-upgrade process. This is a preventive maintenance consideration, not a response to a specific error or failure.

Cause

Offline consistency checks are required only in specific scenarios, such as TarMK upgrades or when there are known repository or index issues. For MongoMK, standard backup and maintenance procedures are recommended unless problems are suspected.

Resolution resolution

Follow the steps below to determine and perform the necessary checks for your AEM deployment:

  1. Identify whether your environment uses TarMK or MongoMK as the persistence layer.

  2. For TarMK deployments:

    • Run offline revision cleanup and segment-store consistency checks before upgrading.
    • Refer to the official AEM upgrade pre-upgrade tasks documentation for details.

  3. For MongoMK deployments:

    • Offline revision cleanup and segment-store consistency checks are not required.
    • Ensure that you have a recoverable backup of the AEM installation, MongoDB data, and the configured datastore.
    • Keep the online Revision Cleanup maintenance task enabled.

  4. For all deployments, regarding index consistency checks:

    • A full offline index consistency check is not mandatory unless there are known issues or index failures.
    • Review the indexing status and logs for any errors.
    • If issues are detected, use the Oak-run tool to perform index consistency checks (levels 1 and 2), which are safe to run on an active AEM instance.

  5. For datastore consistency checks:

    • The need for a datastore consistency check depends on the binary store type (for example, FileDataStore or S3DataStore).
    • For MongoMK, confirm the datastore configuration before selecting a check procedure.
    • Routine offline datastore consistency checks are not required unless there is a concern about data integrity.
recommendation-more-help
experience-cloud-kcs-help-kbarticles