How to Resolve Replication Startup Issue After DR Install
Abotts Logo Abotts Partners with singapore based tech giant to help migrate their public sector customer from Sybase to SQL server.
Upworks Logo Abotts partners with NYPL to integrate with their partner libraries.
Abotts Logo ABOTTS partners with County in Los Angeles to upgrade their court infrastructure into new technologies.
Upworks Logo Upworks Inc partners with ABOTTS to build their Oracle Cloud Infrastructure (OCI) and migrate their custom applications to OCI.
Abotts partners with startup to manage and maintain their IT infrastructure and support SOC2 reporting.
Gnorth Logo Abotts Inc Partners with Gnorth consulting to deploy exadata and ODA for a large public sector customer.
Abotts Logo Abotts Partners with singapore based tech giant to help migrate their public sector customer from Sybase to SQL server.
Upworks Logo Abotts partners with NYPL to integrate with their partner libraries.
Abotts Logo ABOTTS partners with County in Los Angeles to upgrade their court infrastructure into new technologies.
Upworks Logo Upworks Inc partners with ABOTTS to build their Oracle Cloud Infrastructure (OCI) and migrate their custom applications to OCI.
Abotts partners with startup to manage and maintain their IT infrastructure and support SOC2 reporting.
Gnorth Logo Abotts Inc Partners with Gnorth consulting to deploy exadata and ODA for a large public sector customer.

How to Resolve Replication Startup Issue After DR Install

Resolving Replication Server Startup Issue After DR Installation

After completing the installation on the Disaster Recovery (DR) server, we proceeded to run the replication server startup commands to validate the setup and ensure synchronization between the Production and DR environments.

Issue Encountered

While executing the replication server startup commands on the DR server, we encountered an error.
 To Troubleshoot:

  1. We first stopped the replication service and retried the command —we got the same error again  
  2. Next, we started the service again and re-ran the command — still no change.

At this stage, it was clear that the issue was not service-related, but rather environment-specific.

Root Cause

After investigating, we identified that the replication startup commands must be executed on the Production server, not on the DR server. Running them on the DR server caused the errors since the commands depend on the active production environment and its configuration.

Resolution

We took the following corrective steps:

  1. Started the replication service on the Production server.
  2. Executed all required replication startup commands successfully on the Production environment.
  3. Verified the replication status on the DR server after the execution.

Once the commands were correctly executed on the Production server, the replication process initialized successfully, and the DR server reflected the expected status without any further errors.

Important Insights

Always verify the execution environment before running replication or synchronization commands.Commands tied to Production data or configurations must be executed in the Production environment, not on the DR instance.

Reference Document

For detailed guidance on replication setup and failover procedures, refer to the official Progress OpenEdge documentation:
Progress OpenEdge Replication: Configuration and Administration Guide