TarMK not working in Adobe Experience Manager (AEM) On-Premise

The TarMK cold standby setup in Adobe Experience Manager (AEM) experiences synchronization issues between the primary and standby servers. This results in errors such as Segment Not Found on the primary server and Unable to fetch remote head on the standby server. To fix this, check the configurations, ensure network connectivity, and recreate the standby instance if necessary.

Description description

Environment

Adobe Experience Manager (AEM) On-Premise, v6.5

Issue/Symptoms

Cause

The issue resulted from customizations inside the configuration files.

Resolution resolution

Ensure that all configuration files match the documented settings for AEM TarMK Cold Standby. Refer to Creating an AEM TarMK Cold Standby setup in AEM 6.5 User Guide for more details.