Progress OpenEdge Replication is more reliable than ever with the debut of Replication Sets. Find out how you can benefit from this powerful new feature. OpenEdge 11.7 introduces the concept of Replication Sets for disaster recovery plans. We covered all of the new enhancements to OpenEdge Replication in a recent blog post, but we’ll now dive in a little deeper exploring Replication Sets.
In short, a Replication Set is comprised of a source replica and two target replicas that are aware of each other. The awareness allows target replicas to transition together in the event a source replica becomes unavailable or damaged. Target replicas that transition together eliminate a single point of failure in the application environment.
Replication Sets have four important requirements:
• After Imaging must be configured and running on source replicas and both target replicas
• The target replicas must be able to communicate with each other
• The identification of a priority order for target replicas to transition to a source replica
• A property must be set to enable the environment for Replication Sets
OpenEdge has always required that After Imaging is configured and running on source replicas. Replication Sets now require that each target replica has After Imaging configured and running. The presence of After Imaging on target replicas is important as it allows for one of the target replicas to transition to a source replica. The After Imaging data will be used during the transition process to ensure that target replicas are synchronized.
Configuring After Imaging on the target replicas follows the same process as configuring After Imaging on source replicas. You should allocate the same amount of capacity on your target replicas as you do on your source replica. The configuration of After Imaging on a target replica does not need to match the physical layout of After Imaging on the source replica. Nor do target replicas require that their After Imaging configuration match. The target replicas will handle the mapping of After Imaging configurations to the data required to synchronize the targets during a transition process.
The target replicas will need to communicate with each other during the replication process so that the correct mapping of data occurs. The Replication Server will provide the data required for the targets to communicate amongst themselves. The Replication Server gets this data from the control-agent sections of the source’s properties file. It is a best practice to duplicate the source control-agent sections in each of the targets’ properties file. Duplicating the control-agent properties to each target will allow the targets to transition together if the source replica is unable to start up or the source is unable to connect to the targets.
Fail Over and Failure Recovery Transition processes for Replication Sets both need to know which target replica has the priority to transition to a source replica. The target that has priority is identified in the transition section of properties files for each replica using the transition-to-agent property. The value for the transition-to-agent property is a comma separated list that contains the names for agents for target replicas. For our purposes, let’s call our agents targetOne and targetTwo, where targetOne is the agent for the target that we want to have the priority to transition. Our transition-to-agents property would then be: transition-to-agents=targetOne,targetTwo. In the event that targetOne and its replica are not available, then the target for targetTwo has the priority to transition to a source replica.
Enabling a Replication Set
The last configuration task now is to enable the two-target replication environment as a Replication Set. A new property has been added to enable Replication Sets. The new property is replication-set and has two valid values: 0 or 1. The default for the replication-set is 0 and disables Replication Set functionality. The value of 1 enables Replication Set functionality. The property must be placed in the transition section of properties files for each replica for Replication Sets to be enabled. The property is checked by Replication Servers and Replication Agents when they begin, either when the database server is started or when a Server or Agent is restarted using the dsrutil utility.
Eliminate a Single Point of Failure
In conclusion, configuring a replication environment for Replication Sets involves many of the details that OpenEdge Replication users are already familiar with. The ability of Replication Servers to communicate with Replications Agents has been leveraged to allow the agents to communicate with each other. The synchronization process that occurs when Replication Server and Agents startup has been made available for Agents to use when a transition process is wanted or needed. A replication property has been enhanced to support the transition process and one has been added to enable the environment as a Replication Set. All of this together provides for the elimination a single point of failure in OpenEdge Replication environment.
Jeff Owen is Principal Software Engineer OpenEdge and Dapeng Wu is Software Architect OpenEdge at Progress.
20 en 21 maart 2018 We worden al jaren geconfronteerd met een niet-aflatende stroom van nieuwe technologieën, ontwerptechnieken, architecturen en ideeën, zoals Hadoop, streaming, self-service data preparation, logical datawarehouse, d...
27 maart 2018 Wat zijn de mogelijkheden van low code application platformen en hoe kunt u deze succesvol inzetten in uw organisatie? Aan de hand van Microsoft PowerApps, Flow en de Common Data Service wordt besproken maar vooral ook live getoond hoe ...
10 april 2018 API Management gaat enerzijds over het promoten van API’s en anderzijds over het actief ondersteunen van ontwikkelaars bij het gebruik ervan. Tegelijkertijd gaat API Management over het gecontroleerd en centraal beveiligd ont...
11 april 2018Praktisch seminar waarin Sander Hoogendoorn u laat zien hoe u microservices kunt inzetten in uw softwarearchitectuur.Het nieuwste architectuurprincipe microservices lijkt veelbelovend: verkorte time-to-market, schaalbaarheid, autono...
16 mei 2018Workshop met BPM-specialist Christian Gijsels over business analyse, modelleren en simuleren met de nieuwste release van Sparx Systems' Enterprise Architect, versie 13.Intensieve cursus waarin alle basisfunctionaliteiten van Ente...
17 mei 2018 Iedere organisatie heeft te maken met het integreren van systemen en applicaties. Maar welke technologie zet u in bij welke vorm van integratie? Guy Crets bespreekt de verschillende oplossingen voor integratie. Integratie van IT-sys...
30 en 31 mei 2018 Praktische tweedaagse workshop met internationaal gerenommeerde spreker Alec Sharp over herkennen, beschrijven en ontwerpen van business processen. De workshop wordt ondersteund met praktijkvoorbeelden en duidelijke, herbruikbare r...
11 t/m 13 juni 2018Driedaagse workshop over requirements management door James Archer. Opstellen, testen en ondubbelzinnig vastleggen van requirements. Unieke driedaagse workshop over requirements management op basis van de Volere methodiek door Jame...