db-12: achieving high availability with clusters and openedge ® replication
Post on 25-Feb-2016
57 Views
Preview:
DESCRIPTION
TRANSCRIPT
DB-12: Achieving High Availability with Clusters and OpenEdge® ReplicationCombining the two technologies
Hugo Loera ChávezSenior Tech Support Engineer
© 2006 Progress Software Corporation2DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Presentation Goals
To understand how OpenEdge® Enterprise DB works with Clusters.
To understand how OpenEdge Replication works.
To know how to combine Clusters and OpenEdge Replication.
Combining the two technologies
© 2006 Progress Software Corporation3DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Agenda
Combining the two technologies
Why do we need this ?
What is a Cluster ?
How OpenEdge Enterprise DB works with a Cluster?
Overview of OpenEdge Replication
Combining OpenEdge Replication with Clusters
Setting OpenEdge Enterprise DB for High Availability
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation4DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Why do we need this ?
You never know what can happen in your day….
© 2006 Progress Software Corporation5DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Agenda
Combining the two technologies
Why do we need this ?
What is a Cluster ?
How OpenEdge Enterprise DB works with a Cluster?
Overview of OpenEdge Replication
Combining OpenEdge Replication with Clusters
Setting OpenEdge Enterprise DB for High Availability
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation6DB-12 Achieving High Availability with Clusters and OpenEdge Replication
What is a Cluster ?
One possible Cluster definition
A group of loosely coupled computers that work together closely so they can be viewed as a single unit.
© 2006 Progress Software Corporation7DB-12 Achieving High Availability with Clusters and OpenEdge Replication
What is a Cluster ?
Clusters implementations
Supported by Progress
Using OpenEdge Enterprise
RDBMS
The most common implementations are:
• High-availability Clusters
• Load balancing Clusters
• High-performance Clusters
• Massively parallel Clusters
© 2006 Progress Software Corporation8DB-12 Achieving High Availability with Clusters and OpenEdge Replication
What is a Cluster ?
A typical High-availability Cluster setup
Node 2
Application
Operating
System
Cluster Manager
SCSI connection
Storage
Internal network connection
LAN connection
Local StorageNIC
NIC
Node 1
Application
Operating
System
Cluster Manager
Local StorageNIC
NIC
© 2006 Progress Software Corporation9DB-12 Achieving High Availability with Clusters and OpenEdge Replication
What is a Cluster ?
Node 1
Application
Operating System
Local Storage
Cluster Manager
Node 2
Application
Operating System
Local Storage
Cluster ManagerCommon
Storage
DBDB
DB
Node 1 IP Address Node 2 IP Address
Cluster name or
Cluster IPAddress
Cluster connectivityActive Node
© 2006 Progress Software Corporation10DB-12 Achieving High Availability with Clusters and OpenEdge Replication
High-availability Components Cluster Manager
Resources Monitors Heartbeat
What is a Cluster ?
Node 1 Node 2
Common Storage
DBDBDB
MonitorsResources
ClusterManager
Heartbeat
© 2006 Progress Software Corporation11DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Node 2
ClusterManager
Failover process
What is a Cluster ?
Node 1
Common Storage
DBDBDB
XFailover
NewActive Node
© 2006 Progress Software Corporation12DB-12 Achieving High Availability with Clusters and OpenEdge Replication
What do we need to make Clusters work with an OpenEdge DB ?
© 2006 Progress Software Corporation13DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Why do we need this ?
What is a Cluster ?
How OpenEdge Enterprise DB works with a Cluster?
Overview of OpenEdge Replication
Combining OpenEdge Replication with Clusters
Setting OpenEdge Enterprise DB for High Availability
Starting OpenEdge Replicated DB on the Cluster
Agenda
Combining the two technologies
© 2006 Progress Software Corporation14DB-12 Achieving High Availability with Clusters and OpenEdge Replication
It must be installed in each Cluster node. The installation on each node must keep the same directory
structure. PSC_CLUSTER_PATH must point to the OpenEdge installation
directory.
How OpenEdge Enterprise works with a Cluster ?OpenEdge Enterprise installation requirements
Node 1
Application
Operating System
Cluster Manager
Node 2
Application
Operating System
Local Storage
Cluster ManagerCommon
Storage
DBDB
DB
Local StorageOpenEdge Enterprise
DB
OpenEdge Enterprise
DB
© 2006 Progress Software Corporation15DB-12 Achieving High Availability with Clusters and OpenEdge Replication
OpenEdge Enterprise DB 10.1A
OpenEdge Enterprise DB 10.0B01 or higher
How OpenEdge Enterprise works with a Cluster ?Product requirements
© 2006 Progress Software Corporation16DB-12 Achieving High Availability with Clusters and OpenEdge Replication
IBM• HACMP Cluster Manager.
HP• HP MC/ServiceGuard.• TruCluster.
SUN• SUN Cluster
Microsoft• Windows Server Enterprise.
How OpenEdge Enterprise works with a Cluster ?Existing supported Cluster platforms
© 2006 Progress Software Corporation17DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Now, let’s see how OpenEdge Replication works
© 2006 Progress Software Corporation18DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Agenda
Combining the two technologies
Why do we need this ?
What is a Cluster ?
How OpenEdge Enterprise DB works with a Cluster?
Overview of OpenEdge Replication
Combining OpenEdge Replication with Clusters
Setting OpenEdge Enterprise DB for High Availability
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation19DB-12 Achieving High Availability with Clusters and OpenEdge Replication
To have a hot spare DB.
To offload reporting from the production DB.
Overview of OpenEdge Replication
What is OpenEdge Replication used for ?
Overview of OpenEdge Replication
© 2006 Progress Software Corporation20DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Overview of OpenEdge Replication
Replicated remote site
Site BSite A
Source DB
After Image
Replication
Server
R/OTarget
DB
Replication
Agent
Remote Link
AI BufferAIBlock
© 2006 Progress Software Corporation21DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Overview of OpenEdge Replication
Site BSite A
After Image
Target DB
X
Transition to Site B
Source DB
© 2006 Progress Software Corporation22DB-12 Achieving High Availability with Clusters and OpenEdge Replication
OpenEdge Enterprise DB 10.1A with:• OpenEdge Replication 10.1A• OpenEdge Replication plus 10.1A
OpenEdge Enterprise DB 10.0B01 or higher with:• Fathom Replication 10.0B• Fathom Replication plus 10.0B
Product requirements
Overview of OpenEdge Replication
© 2006 Progress Software Corporation23DB-12 Achieving High Availability with Clusters and OpenEdge Replication
OpenEdge Enterprise and Replication must be installed together at:
• The source DB host.
• The target DB host.
The source DB host and the target must have the same OpenEdge Release.
Overview of OpenEdge Replication
Installation requirements
Overview of OpenEdge Replication
© 2006 Progress Software Corporation24DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Allows to use the replicated data in read-only mode.
It allows to offload reporting from the production DB.
Additional benefits when using OpenEdge Replication Plus
Overview of OpenEdge Replication
© 2006 Progress Software Corporation25DB-12 Achieving High Availability with Clusters and OpenEdge Replication
ReplicationAfterImage
The regular backup routine is still required.
OpenEdge Replication adds another protection layer to the regular DB backup strategy.
How will the DB backup strategy work with
OpenEdge Replication ?
DBBackup
Overview of OpenEdge Replication
© 2006 Progress Software Corporation26DB-12 Achieving High Availability with Clusters and OpenEdge Replication
How can we mix OpenEdge Enterprise DB, OpenEdge Replication and a Cluster ?
© 2006 Progress Software Corporation27DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Agenda
Combining the two technologies
Why do we need this ?
What is a Cluster ?
How OpenEdge Enterprise DB works with a Cluster?
Overview of OpenEdge Replication
Combining OpenEdge Replication with Clusters
Setting OpenEdge Enterprise DB for High Availability
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation28DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Combining OpenEdge Replication with ClustersHigh availability configuration diagram
Node 1
DB Broker
Operating System
Cluster Manager Common
Storage
Local StorageOpenEdge Enterprise
DB & Replication
Node 2
Operating System
Cluster Manager
Local StorageOpenEdge Enterprise
DB & Replication
Target DB
Replication AgentReplication
Server
OpenEdge Enterprise
& Replication
Source DB
Site A
Site B
© 2006 Progress Software Corporation29DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Combining OpenEdge Replication with ClustersHardware failure on Node 1
Node 1
Operating System
Cluster Manager Common
Storage
Local StorageOpenEdge Enterprise
DB & Replication
Node 2
Operating System
Cluster Manager
Local StorageOpenEdge Enterprise
DB & Replication
Target DB
Replication AgentReplication
Server
OpenEdge Enterprise
& Replication
Source DB
Site A
Site B
DB Broker
X
© 2006 Progress Software Corporation30DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Combining OpenEdge Replication with ClustersCommon Storage or Site failure
Common Storage
Node 2
Operating System
Cluster Manager
Local StorageOpenEdge Enterprise
DB & Replication
DB
DB Broker
OpenEdge Enterprise
& Replication
Source DB
Site A
Site B
Node 1
Operating System
Cluster Manager
Local StorageOpenEdge Enterprise
DB & Replication
X X X
© 2006 Progress Software Corporation31DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Cluster offers:• Elimination of individual computer as a single point of
failure.• Quick response in case of a hardware failure.
Replication offers:• Removal of the DB as a single point of failure.• Elimination of the central storage as a single point of
failure.• Site failure protection.• Access to up to two replicated DB’s.
Combining OpenEdge Replication with ClustersWhy integrate Clusters with OpenEdge Replication ?
© 2006 Progress Software Corporation32DB-12 Achieving High Availability with Clusters and OpenEdge Replication
How do we configure all this ?
© 2006 Progress Software Corporation33DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Agenda
Combining the two technologies
Why do we need this ?
What is a Cluster ?
How OpenEdge Enterprise DB works with a Cluster?
Overview of OpenEdge Replication
Combining OpenEdge Replication with Clusters
Setting OpenEdge Enterprise DB for High Availability
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation34DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Let’s set a source and a target DB called Demo.
• The source Demo DB will reside in the Cluster.• The target Demo DB will reside in a remote host.
Setting OpenEdge Enterprise for High Availability
Example
© 2006 Progress Software Corporation35DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Configuring procedure flow diagram
Create Source DB
Backup DB
Enable AI
Enable Source Replication
Incremental Backup
Create Target DB
Restore DB andIncremental
Enable Target Replication
Start Target DB
Start Source DB
ProCluster enable
Source DB
Start Clustered Source DB
Start Target DB
Stop Source DB
Stop Target DB
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation36DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Creating the source Demo DB at the Cluster site A
Node 1
Common Storage
Local StorageOpenEdge Enterprise
DB & Replication
Node 2
Local StorageOpenEdge Enterprise
DB & Replication
Source Demo
Site A
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation37DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Create a DB in a directory within the shared storage device.
Add After Image extents as required.
Copy from %DLC%\properties:source.repl.properties into the DB directory.
Rename it as Demo.repl.properties
Creating the source Demo DB
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation38DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Source Demo DB files
Demo DB
Demo.DB
Demo.d1
Demo.b1
Demo_7.d1
Demo_8.d1
Demo.a1Demo.a1Demo.a1
+Demo.repl.properties
Source DB Replication
Properties File
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation39DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Define the replication agent name.
Define the target DB host name.
Define target DB port number.
Demo Source DB Replication Properties File
[server] control-agents=agent1 database=Demo transition=manual transition-timeout=600
[control-agent.agent1] name=agent1 database=target host=remotehost port=4501 connect-timeout=120 replication-method=async critical=0
Demo.repl.properties file
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation40DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Perform a probkup of the Demo DB.
Run rfutil Demo -C aimage begin
Run proutil Demo -C enablesitereplication source
Perform incremental probkup of the DB
Enabling Demo DB as the source
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation41DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Creating the target Demo
DB at the remote site B
Target Demo
OpenEdge Enterprise
DB & Replication
Site B
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation42DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Create a structure for the target DB Demo into the DB directory.
Restore Source DB backup and incremental.
Copy from %DLC%\properties:target.repl.properties into the DB directory.
Rename it as Demo.repl.properties
Creating Demo DB as the target
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation43DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Define the replication agent name Define the target DB name
[agent]
name=agent1
database=Demo
listener-minport=4387
listener-maxport=4500
Demo.repl.properties file
Demo Target DB Replication Properties File
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation44DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Target DB Demo files
Demo DB
Demo.DB
Demo.d1
Demo.b1
Demo_7.d1
Demo_8.d1
Demo
Backup
IncrementalBackup
Demo.repl.properties
Target DB Replication
Properties File +
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation45DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Run:• proutil Demo -C enableSiteReplication target
Run:• proserve -db Demo -DBService replagent -S 4501
In the Cluster site A, where the Source is, run:• proserve -db Demo -DBService replserv
Starting the target and source DB Demo
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation46DB-12 Achieving High Availability with Clusters and OpenEdge Replication
When the replication process starts, the source DB log shows:• The Fathom Replication Server has successfully connected to the Fathom Replication Agent agent1 on host remotehost. (10507)
When replication has been established the source DB log shows:• The source database Demo and the target database E:\DB\Demo on host remotehost are synchronized. (10436)
Verifying that replication has been accomplished by viewing in the log file.
Setting OpenEdge Enterprise for High Availability
© 2006 Progress Software Corporation47DB-12 Achieving High Availability with Clusters and OpenEdge Replication
How do we start the replicated Source Demo DB as a clustered resource and keep the
replication running?
© 2006 Progress Software Corporation48DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Agenda
Combining the two technologies
Why do we need this ?
What is a Cluster ?
How OpenEdge Enterprise DB works with a Cluster?
Overview of OpenEdge Replication
Combining OpenEdge Replication with Clusters
Setting OpenEdge Enterprise DB for High Availability
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation49DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Starting OpenEdge Replicated DB on the Cluster
Enabling and Starting the Clustered source DB
Node 1
DB Broker
Operating System
Cluster Manager Common
Storage
Local StorageOpenEdge Enterprise
DB & Replication
Node 2
Operating System
Cluster Manager
Local StorageOpenEdge Enterprise
DB & Replication
Target Demo
OpenEdge Enterprise
DB & Replication
Source Demo
Site A
Site B
Replication AgentReplication
Server
© 2006 Progress Software Corporation50DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Shut down Source and Target DB’s
Create a source .pf file (required for the Cluster) • Set the following parameters in Demo.pf :
– -cluster protected– -DBService replserv
procluster e:\DB\Demo enable –pf Demo.pf
Registering the source DB with the Cluster Manager
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation51DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Starting OpenEdge Replicated DB on the Cluster
Starting the clustered Source DB
Procluster DB start
Cluster
Manager
Cluster Manager
Starts Protected
Resource
DB is
Started_mprosrv
© 2006 Progress Software Corporation52DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Start target DB’s using:
• proserve -db Demo -DBService replagent -S 4501
Start source DB’s using:
• procluster e:\DB\Demo start
Verify replication synchronization in the log.
Registering the source DB with the Cluster Manager
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation53DB-12 Achieving High Availability with Clusters and OpenEdge Replication
When the replication process starts, the source DB log shows:• The Fathom Replication Server has successfully connected to the Fathom Replication Agent agent1 on host remotehost. (10507)
When replication has been established the source DB log shows:• The source database Demo and the target database E:\DB\Demo on host remotehost are synchronized. (10436)
Now we take a look again to the source Demo.lg to verify that replication has been accomplished.
Starting OpenEdge Replicated DB on the Cluster
© 2006 Progress Software Corporation54DB-12 Achieving High Availability with Clusters and OpenEdge Replication
In Summary
Working with OpenEdge Enterprise and Clusters offers quick recovery from hardware failures.
OpenEdge Replication protects us in case of a site down situation.
The combination of both allow protection from several disaster scenarios.
© 2006 Progress Software Corporation55DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Questions?
© 2006 Progress Software Corporation56DB-12 Achieving High Availability with Clusters and OpenEdge Replication
Thank you foryour time
© 2006 Progress Software Corporation57DB-12 Achieving High Availability with Clusters and OpenEdge Replication
top related