Try OpenEdge Now
skip to main content
User Guide
Moving From Failure to Recovery with OpenEdge Replication : OpenEdge Replication from normal activity through failure and recovery : Step 2: Primary machine failure
 

Step 2: Primary machine failure

Replication activity continues until a failure occurs on the primary machine, as shown in the following figure.
Figure 14. Primary machine failure
The Replication agent recognizes the failure as a TCP/IP communication error. Typical failures might be due to a network outage between the primary and secondary machines, a primary database crash, or a primary hardware crash.
Note: Shutting down either the source or target database using PROSHUT without a forced shutdown is considered a normal event and not a failure by either the OpenEdge Replication server or agent. Additionally, if the OpenEdge Replication server is terminated with DSRUTIL db-name -C terminate server or the OpenEdge Replication agent is terminated with DSRUTIL db-name -C terminate agent, it is also not considered a failure.