DB-2: OpenEdge® Replication: How to get Home in Time … Brian Bowman Sr. Solutions Engineer Sandy...
-
Upload
sheila-webster -
Category
Documents
-
view
228 -
download
0
Transcript of 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
© 2007 Progress Software Corporation3 DB-2: OpenEdge® Replication: How to get Home in Time …
OpenEdge Business Continuity Solutions
© 2007 Progress Software Corporation4 DB-2: OpenEdge® Replication: How to get Home in Time …
OpenEdge Replication Plus
© 2007 Progress Software Corporation5 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation6 DB-2: OpenEdge® Replication: How to get Home in Time …
Sample Image:
Please replace it
(Insert, Picture, …)
Protecting Your Future
Replication Overview OpenEdge Replication Process Failover, Secondary Replication, and Failback
details Summary
© 2007 Progress Software Corporation7 DB-2: OpenEdge® Replication: How to get Home in Time …
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.
© 2007 Progress Software Corporation8 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation9 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation10 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation11 DB-2: OpenEdge® Replication: How to get Home in Time …
OpenEdge ReplicationComplete Configuration
Primary Secondary
SourceDatabase
TargetDatabase
Database Broker
Processes
Database Broker
Processes
AI Extents
Repl Queue Repl AgentRepl Server
© 2007 Progress Software Corporation12 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation13 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation14 DB-2: OpenEdge® Replication: How to get Home in Time …
Primary Target One
SourceDatabase
Repl Agent
Modes of ReplicationAsynchronous
TargetDatabase
Repl Agent
TargetDatabase
Target Two
© 2007 Progress Software Corporation15 DB-2: OpenEdge® Replication: How to get Home in Time …
Primary Secondary
SourceDatabase
Repl Agent
Modes of ReplicationSynchronous
TargetDatabase
© 2007 Progress Software Corporation16 DB-2: OpenEdge® Replication: How to get Home in Time …
Primary SecondarySource
Database
Database Broker
Processes
AI Extents
Repl Queue
Repl AgentRepl Server
OpenEdge Replication Failure Conditions
X
TargetDatabase
Database Broker
Processes
XX
© 2007 Progress Software Corporation17 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation18 DB-2: OpenEdge® Replication: How to get Home in Time …
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”
© 2007 Progress Software Corporation19 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation20 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation21 DB-2: OpenEdge® Replication: How to get Home in Time …
Replication Configuration Properties
[server]
…
[control-agent.DELTA]
…
[transition]
…
[agent]
…
[agent]
…
[transition]
…
[server]
…
[control-agent.DELTA]
…
Primary Property File Secondary Property File
© 2007 Progress Software Corporation22 DB-2: OpenEdge® Replication: How to get Home in Time …
Sample Image:
Please replace it
(Insert, Picture, …)
Protecting Your Future
Replication Overview OpenEdge Replication Process Failover, Secondary Replication, and Failback Summary
© 2007 Progress Software Corporation23 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation24 DB-2: OpenEdge® Replication: How to get Home in Time …
Enabling OpenEdge Replication
Replication enabled
Pri
ma
ryS
eco
nd
ary
© 2007 Progress Software Corporation25 DB-2: OpenEdge® Replication: How to get Home in Time …
Failover Time Line
Replication enabled
Pri
ma
ryS
eco
nd
ary
© 2007 Progress Software Corporation26 DB-2: OpenEdge® Replication: How to get Home in Time …
Primary Replication Configuration Properties
[server]
control-agents=DELTA
database=ALPHA
[control-agent.DELTA]
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
Primary Property File Secondary Property File
© 2007 Progress Software Corporation27 DB-2: OpenEdge® Replication: How to get Home in Time …
Additional Configuration Properties
[server]
transition=manual
transition-timeout=60
defer-agent-startup=720
agent-shutdown-action=recovery
[control-agent.DELTA]
replication-method=async
critical=0
name=secondary
[agent]
connect-timeout=600
listener-minport=10024
listener-maxport=20000
Primary Property File Secondary Property File
© 2007 Progress Software Corporation28 DB-2: OpenEdge® Replication: How to get Home in Time …
Failover Time Line
Replication enabled
Source fails
Transitionto source
Pri
ma
ryS
eco
nd
ary
© 2007 Progress Software Corporation29 DB-2: OpenEdge® Replication: How to get Home in Time …
Deployment – Fail Over
Manual• Transition target to production
dsrutil target -C transition agent Auto
• Database is automatically transitioned to production
Start target database server
© 2007 Progress Software Corporation30 DB-2: OpenEdge® Replication: How to get Home in Time …
Failover Time Line
FR enabled
Source fails
Transitionto source
Updates begin
Pri
ma
ryS
eco
nd
ary
Target shutdownand re-started
© 2007 Progress Software Corporation31 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation32 DB-2: OpenEdge® Replication: How to get Home in Time …
Failover Time LineReplication enabled
Transitionto source
Updates begin
Target shutdownand re-started
Pri
ma
ryS
eco
nd
ary
Onlinebackup
Restore backupSource fails
© 2007 Progress Software Corporation33 DB-2: OpenEdge® Replication: How to get Home in Time …
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
Primary Property File Secondary Property File
© 2007 Progress Software Corporation34 DB-2: OpenEdge® Replication: How to get Home in Time …
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
Primary Property File Secondary Property File
© 2007 Progress Software Corporation35 DB-2: OpenEdge® Replication: How to get Home in Time …
Failover Time LineReplication enabled
Transitionto source
Updates begin
Target shutdownand re-started
Reverse roles
Pri
ma
ryS
eco
nd
ary
Onlinebackup
Restore backupSource fails
© 2007 Progress Software Corporation36 DB-2: OpenEdge® Replication: How to get Home in Time …
Failover Time Line
Replication enabled
Source fails
Transitionto source
Updates begin
Target shutdownand re-started
Reverse roles
Pri
ma
ryS
eco
nd
ary
Onlinebackup
Target & Sourceshutdown & re-started
Restore backup
© 2007 Progress Software Corporation37 DB-2: OpenEdge® Replication: How to get Home in Time …
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]
© 2007 Progress Software Corporation38 DB-2: OpenEdge® Replication: How to get Home in Time …
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?
© 2007 Progress Software Corporation39 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation40 DB-2: OpenEdge® Replication: How to get Home in Time …
Online transitions AI automation
• Extent add
• Start
Auto DB control• Shutdown after transition
• Auto restart
OpenEdge Replication Enables…
© 2007 Progress Software Corporation41 DB-2: OpenEdge® Replication: How to get Home in Time …
Replication also enables…
Scheduled system maintenance capabilities Reporting on Target Database
© 2007 Progress Software Corporation42 DB-2: OpenEdge® Replication: How to get Home in Time …
In Summary
Protect your business Protect your data Protects your future with
OpenEdge Replication
© 2007 Progress Software Corporation43 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation44 DB-2: OpenEdge® Replication: How to get Home in Time …
Questions?
© 2007 Progress Software Corporation45 DB-2: OpenEdge® Replication: How to get Home in Time …
Thank you for your time!
© 2007 Progress Software Corporation46 DB-2: OpenEdge® Replication: How to get Home in 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
© 2007 Progress Software Corporation47 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation48 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation49 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation50 DB-2: OpenEdge® Replication: How to get Home in Time …
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
© 2007 Progress Software Corporation51 DB-2: OpenEdge® Replication: How to get Home in Time …