1. OE REPLICATION AKA FATHOM REPLICATION

2. WHO AM I Currently with Eaton Corp as a Sr. Progress DBA for the past 12 years Started Programming with Progress in 1989, version 4.2 Progress Consultant/DBA for over 18 years. Currently administrate over 95 plants in 50+ environments (5-7 db’s each, over 300) Sizes range from 25GB to 460GB

3. WHAT IS REPLICATION This is a feature/product from Progress that provides real-­Time synchronization between two or more databases. There is a replication server(source) and one or more replication agents (targets).

4. PROS AND CONS OF OE REPLICATION Pros Supported from 10.1 and above Real-time replication Reporting on Target Cons Not Cheap Learning Curve Setup on large DB’s takes a long time

5. WHAT AND WHY SHOULD I SPEND THE $$$ Source DB Target DB 2 Target DB 1 After Image Files Repl Server Repl Agent Clients Process

6. DIFFERENT TYPES True failover – Run two exact same servers that contain everything that is kept in sync. Could still have corrupt data. Partial failover – Run core software on failover server and restart production DB. Poor man Replication – Apply AI notes every X mins to a standby database. OpenEdge Replication Can be on same or different server. ONLY replicates databases.

7. BEST SOLUTION A combined solutions is BEST. And most expensive. But if your data is really needed and zero loss data is the target, then a combine solution is the choice. Two Servers that are configured the same. OS and other files are kept in sync using a heartbeat or tools like rsync OE Replication is used to keep databases in sync OE Replication Plus is used to allow reporting on the target. ODBC is connected only to the Target

8. TWO SYSTEMS VS. ONE SYSTEM Keep OS levels the same on both systems Keep supporting files like kernal, services etc in sync. All software need to be in sync (progress, edi, erp, accounting) ONE system If you have a hardware failure you are done. System can be over used and slow production down.

9. OUT OF THE BOX FAILOVER This means you will be failing over all users to another server on crash. You may use aliases to setup server names to all clients to connect. Production server contains all software and datrabases Failover Server contains all software and replicated databases Cleint Connection ODBC Connection Reporting Connection Cleint Connection

10. EATONS’ VERSION FAILOVER This means you will be failing over all users to another server on server crash only. Production databases will allows be on production server. Production server contains all software and datrabases Failover Server contains all software and replicated databases ODBC Connection Reporting Connection Cleint Connection

11. EATONS’ VERSION DATABASE FAILOVER Database is shutdown (source/target) Target to snapped and copied to Production server and made into source. And started up. Production server contains all software and datrabases Failover Server contains all software and replicated databases ODBC Connection Reporting Connection Cleint Connection

12. EATONS’ VERSION SYSTEM FAILOVER Failover server is renamed to Production server. Target to snapped and copied to Production server and made into source. And started up. Production (old Failover) Server contains all software and replicated databases ODBC Connection Reporting Connection Cleint Connection

13. WITHOUT REPLICATION After image Files are taken from the source machine and applied throughout the day Pros: – Cheap Cons: – Not synchronous – Must maintain the code yourself ONLY as GOOD as you code it,

14. SOURCE SIDE SETUP AI must be turned on. (this should be already on) With the database down you need to enable site replication for the source database. proutil –C enablesitereplication source Move the new properties file into place Currently the same directory as the DB Start the source database with -DBService replserv parameter Do an online backup of the source Restore The Backup To the target

15. TARGET SIDE SETUP Restore backup to target database. Enable replication on target proutil –C enablesitereplication target! Or prorest -REPLTransition (I have never TRIED THIS) Start the target with -DBService replagent and –S parameters Use the dsrutil command to monitor dsrutil –C monitor Or look for the following message in the target database.lg file The Source and Target databases are synchronized. (10668).

16. NEW PROPERTIES FILES Server Properties Agent Properties

17. SERVER PROPERTIES [server] control-agents=phramfg_agent database=phrpmfg transition=manual transition-timeout=1200 defer-agent-startup=600 [control-agent.phramfg_agent] name=phramfg_agent database=phramfg host=phrqa.tcc.etn.comHost of Failover DB port=phramfg connect-timeout=3600 replication-method=async critical=0

18. AGENT PROPERTIES $more phramfg.repl.properties [agent] name=phramfg_agent database=phrpmfg listener-minport=63460 listener-maxport=63999 [transition] database-role=normal

19. DSRUTIL MONITOR OpenEdge Replication Monitor Page 1 Database: /mfgpro/nhb/db1/nhbpmfg Database is enabled as OpenEdge Replication: Source Server is: In Normal Processing Number of configured agents: 1 Delay Interval (current / min / max): 365 / 5 / 500 Recovery information: State: No recovery being performed Agents needing recovery: 0 Agents connected: 0 Agents in synchronization: 0 Transition information: Type: Manual

20. DSRUTIL MONITOR R. Replication server remote agents OpenEdge Replication Monitor Page 1 Database: /mfgpro/nhb/db1/nhbpmfg Database is enabled as OpenEdge Replication: Source Remote Agents Configured: ID Name Host Name Database 1. nhbamfg_agent 151.110.228.88 /mfgoer/nhb/db1/nhbamfg Q. Quit

21. DSRUTIL MONITOR TARGET Database: /mfgoer/nhb/db1/nhbamfg Database is enabled as OpenEdge Replication: Target Agent: Name: nhbamfg_agent ID: 1 Host name: 151.110.230.42 State: Normal Processing Ready: Yes Critical: No Method: Asynchronous Agent is waiting for: Nothing Maximum bytes in TCP/IP message: 8504 Server/Agent connection time: Sun Oct 12 00:15:17 2014 Delay Interval (current / min / max): 5 / 5 / 500 Transition information: Type: Manual The last block received at: Mon Oct 13 09:24:40 2014 Activity information: Blocks received: 1060208 Blocks processed: 1060208

22. DSRUTIL MONITOR TARGETPART 2 Blocks acknowledged: 0 Notes processed: 90094997 Transactions started: 2486493 Transactions ended: 2486486 Synchronization points: 649 AI Block Information: Source RDBMS Block (Seq / Block): 31835 / 172 Last Processed Block (Seq / Block): 31835 / 170 Latency Information: Repl Server behind Source DB by: 0 second(s) Current Source Database Transaction: 266920035 Last Transaction Applied to Target: 266920034 Target Current as of (Target, Source): Mon Oct 13 09:24:40 2014, Mon Oct 13 09:24:40 2014 with delta of 000:00:00

23. MANY OPTIONS OF DSRUTIL applyextent! Manual application of source AI extents to the target database. Canceldefer Do not attempt reconnect to deferred replication agent. connectagent or startagent Start agent(s). Disablesitereplication Online disable of replication on the source database. Recovery Displays the replication recovery information. Relwaits Release any waits so that database activity can continue. restart! Restart replication server. Terminate Terminates replication server or agent. Transition Transition agent to a replication-enabled database. Triggertransition Places the target database into a pre-transition state.

24. FAILOVER. Replication agent on target machine enters pretransition. If the server properties has agent-shutdown-action set as normal, the agent will shut down. When this happens, you will need to manually enter pretransition dsrutil target -C triggertransition at this point, try to apply all unapplied AI extents to secondary database (for manual transition only, if auto transition, could lose unapplied AI extents) dsrutil target -C recovery dsrutil target -C applyExtent extent_name 4. Transition target to primary Automatic: if the properties file is configuring this as automatic, auto transition occurs Manual: dsrutil target -C transition

25. AI FILE TYPES Empty – Ready and unused Busy – Currently in use Full – Being applied and once done will switch to emtpy. Locked – Waiting to be applied

26. AI FILE TYPES Extent: 1 Status: Busy Type: Variable Length Path: /AIpro/nhb/nhbpmfg.a1 Size: 7800 Used: 7777 Start: Mon Oct 13 09:54:53 2014 Seqno: 31837 Extent: 2 Status: Empty Type: Variable Length Path: /AIpro/nhb/nhbpmfg.a2 Size: 120 Used: 0 Start: N/A Seqno: 0

27. THE END