db-2: openedge® replication: how to get home in time … brian bowman sr. solutions engineer sandy...

DB-2: OpenEdge® Replication: How to get Home in Time …

Brian BowmanSr. Solutions Engineer

Sandy CaiadoSr. Solutions Engineer

© 2007 Progress Software Corporation2 DB-2: OpenEdge® Replication: How to get Home in Time …

Sample Image:

Please replace it

(Insert, Picture, …)

OpenEdge Protecting Your Future

Replication Overview OpenEdge Replication Process Failover, Secondary Replication and Failback

details Questions


OpenEdge Business Continuity Solutions


OpenEdge Replication Plus


OpenEdge Replication

Near real-time replication• Near zero-latency

• No data loss

• Guaranteed data integrity

Flexible database options• Multiple target databases

• Read-only query access

Easy deployment Automatic recovery

Continuous Availability With


Sample Image:

Please replace it


Protecting Your Future

Replication Overview OpenEdge Replication Process Failover, Secondary Replication, and Failback

details Summary


Definitions

Source database • “Normal” production

• Original source of updates

Target database• Standby database

• Target location in OpenEdge Replication

Single point of failure – a bad thing.


Definitions

Primary Replication • Normal processing

• Primary machine performs updates

• Secondary machine receives updates

Failover• Primary machine fails

• Secondary machine becomes primary

No Backup – a bad thing


Definitions

Secondary Replication• Failed over mode• Secondary machine performs updates• Primary machine receives updates

Failback• The process to get primary machine back to

its original state and the secondary machine to take on its original role to be the backup

Failing to check your backup – a bad thing


Definitions

Transition• Process where the databases change roles

• Configured to be either manual or automatic

Synchronization• Process to make sure the database on

primary and secondary are identical

• This is performed– During database and replication startup– Failure recovery processing


OpenEdge ReplicationComplete Configuration

Primary Secondary

SourceDatabase

TargetDatabase

Database Broker

Processes

Database Broker

Processes

AI Extents

Repl Queue Repl AgentRepl Server


OpenEdge ReplicationFunctionality

Primary Primary

SourceDatabase

AI Extents

Repl Queue

Repl Server

Configures and manages remote agents

Sends all database activity to its replication agents

Controls replication agents

Database Broker

Processes


OpenEdge ReplicationFunctionality

Secondary

Repl Agent

Receives database activity from replication server

Performs continuous roll-forward to target database

Types of Agents• Asynchronous

• SynchronousTarget

Database

Database Broker

Processes


Primary Target One

SourceDatabase

Repl Agent

Modes of ReplicationAsynchronous

TargetDatabase

Repl Agent

TargetDatabase

Target Two


Primary Secondary

SourceDatabase

Repl Agent

Modes of ReplicationSynchronous

TargetDatabase


Primary SecondarySource

Database

Database Broker

Processes

AI Extents

Repl Queue

Repl AgentRepl Server

OpenEdge Replication Failure Conditions

X

TargetDatabase

Database Broker

Processes

XX


How Does it Work?

Plugs into after-image sub-system TCP connection between server and agent Queue for transfers on source Agent periodically (every 10 blocks) polls

server for heart beat (asynchronous mode) Agent will also communicate a

synchronization point (ie. extent switch) back to the server


Additional Considerations

Schema changes are replicated AI extents must be managed

• AI Management Utility!!! Ensure that you have enough AI extents

space - extents will remain “locked” until they are replicated in entirety

PSDN Whitepaper – “Managing AI with and OpenEdge Replication”


Machine Setup

Source and target machines must • Have identical architectures

• Be running the same operating system

• Be connected via TCP/IP

The target machine must have disk space comparable to the source machine


Progress Requirements

Progress 9.1E for Fathom Replication 3.0A OpenEdge 10.0B+ for OpenEdge Replication

(failback capabilities enable in 10.1A) After-imaging must be enabled


Replication Configuration Properties

[server]

…

[control-agent.DELTA]

…

[transition]

…

[agent]

…

[agent]

…

[transition]

…

[server]

…


…

Primary Property File Secondary Property File


Sample Image:

Please replace it


Protecting Your Future

Replication Overview OpenEdge Replication Process Failover, Secondary Replication, and Failback Summary


Replication ModesP

rim

ary

Se

con

dar

y

Pri

mar

y R

eplic

atio

n

Sec

on

dar

y R

eplic

atio

n

Pri

mar

y R

eplic

atio

n


Enabling OpenEdge Replication

Replication enabled

Pri

ma

ryS

eco

nd

ary


Failover Time Line

Replication enabled

Pri

ma

ryS

eco

nd

ary


Primary Replication Configuration Properties

[server]

control-agents=DELTA

database=ALPHA


name=DELTA

database=BRAVO

host=nbPrimary

port=4501

proserve ALPHA

–S <DB Port>

–DBService replserv

[agent]

name=DELTA

database=BRAVO

proserve BRAVO

–S 4501

–DBService replagent



Additional Configuration Properties

[server]

transition=manual

transition-timeout=60

defer-agent-startup=720

agent-shutdown-action=recovery


replication-method=async

critical=0

name=secondary

[agent]

connect-timeout=600

listener-minport=10024

listener-maxport=20000



Failover Time Line

Replication enabled

Source fails

Transitionto source

Pri

ma

ryS

eco

nd

ary


Deployment – Fail Over

Manual• Transition target to production

dsrutil target -C transition agent Auto

• Database is automatically transitioned to production

Start target database server


Failover Time Line

FR enabled

Source fails

Transitionto source

Updates begin

Pri

ma

ryS

eco

nd

ary

Target shutdownand re-started


Automated FailbackTransition Configuration Properties

[transition]

transition-to-agent=BRAVO

database-role=reverse

auto-begin-ai=1

auto-add-ai-areas=1

ai-structure-file=primaryai.st

restart-after-transition=1

source-startup-arguments= -pf primary.source.pf

target-startup-arguments= -pf primary.target.pf

backup-method=full-offline

backup-arguments=secondary.bak

incremental-backup-arguments=secondary.incr.bak

Key:

Agent Management

After Image Management

Database Management

Backup Management

Property File Transition Section


Failover Time LineReplication enabled

Transitionto source

Updates begin


Pri

ma

ryS

eco

nd

ary

Onlinebackup

Restore backupSource fails


Secondary Replication Configuration Properties

[server]

control-agents=ECHO

database=BRAVO

[control-agent.ECHO]

name=ECHO

database=ALPHA

host=nbSecondary

port=4501

proserve BRAVO

–S <DB Port>

–DBService replserv

[agent] name=ECHO database=ALPHA

proserve ALPHA –S 4501 –DBService replagent



Additional Secondary Replication Properties

[agent] listener-minport=10024 listener-maxport=20000 connect-timeout=600

[server]transition=autotransition-timeout=60name=primarydefer-agent-startup=720agent-shutdown-action=recovery

[control-agent.ECHO]replication-method=asyncconnect-timeout=600critical=0



Failover Time LineReplication enabled

Transitionto source

Updates begin


Reverse roles

Pri

ma

ryS

eco

nd

ary

Onlinebackup

Restore backupSource fails


Failover Time Line

Replication enabled

Source fails

Transitionto source

Updates begin


Reverse roles

Pri

ma

ryS

eco

nd

ary

Onlinebackup

Target & Sourceshutdown & re-started

Restore backup


Replication Failback Transition

Databases can be • Synchronized• shut down• Transitioned to new roles• AI added and enabled• and restarted

with a single command Process is initiated from the source database

side

DSRUTIL database –C transition [failover]


Replication Failback Transition

Transition based on the properties files Transition will occur based on the following

criteria:• Source or target

• Online or offline

• Is Replication Server or Agent running?

• Has failure just occurred?


Replication ModesP

rim

ary

Se

con

dar

y

Pri

mar

y R

eplic

atio

n

Sec

on

dar

y R

eplic

atio

n

Pri

mar

y R

eplic

atio

n


Online transitions AI automation

• Extent add

• Start

Auto DB control• Shutdown after transition

• Auto restart

OpenEdge Replication Enables…


Replication also enables…

Scheduled system maintenance capabilities Reporting on Target Database


In Summary

Protect your business Protect your data Protects your future with

OpenEdge Replication


Where to go from here

Other Exchange sessions:• COMP-10 OpenEdge Management and Replication –

Divide et impera! (June 13, 8am)• COMP-15 Disaster Recovery Planning (June 13,

3:30pm)

PSDN• http://www.psdn.com/library/kbcategory.jspa?categoryI

D=555• Whitepapers!

Professional Services for assistance


Questions?


Thank you for your time!


1. Primary database is Lost• Determine which ai extents to apply

dsrutil target -C recovery

• Manually apply source AI extents on target (Optional)dsrutil db –C applyextent

2. Secondary database transition• Source or normal / online or offline

dsrutil db –C transition

3. AI extents added and AI started[normal AI enablement process]

4. Secondary restarted• Manual or automatic

proserve …

5. Awaits communication to Primary

OpenEdge Replication Release 10Failover Process


OpenEdge Replication Release 10.1B Enable Secondary Replication

Primary machine repaired Online backup of secondary db Copy backup to primary machine Make db on primary machine the target

prorest primary bkupfile [–REPLTransition]

DB on secondary machine acting as source and replicating to target on primary


OpenEdge Replication Release 10.1B Failback Specifics

Schedule time to get db on primary machine transitioned back to source

No activity on either machine 2 methods:

• Automated Failback

• Controlled Transition

On secondary machine:dsrutil secondary –C transition failover


FailbackAutomated Failback

Initiated on Source database (on Secondary machine)• <insert command>

Ensures databases are in sync Backs up databases (periodically for recovery) Shuts down database Does AI management (if requested) Reverses Roles Finishes AI management (if requested) Restarts Databases


FailbackControlled Transition

Controlled Transition• Verify synchronization:

– Look at db log file or– Dsrutil source –C status –detail– Shutdown databases– On primary machine transition to source

Dsrutil primary –C transition

– On secondary machine transition to target Dsrutil secondary –C transition

db-2: openedge® replication: how to get home in time … brian bowman sr. solutions engineer sandy...

Documents

progress software corporation

updatessecondary machine

modesecondary machine

updatesprimary machine

performedduring database

bad thing

original state

original role