Presentation is loading. Please wait.

Presentation is loading. Please wait.

COMP-13: The “Weakest-Link” in your High Availability system How to make sure your HA is really highly available Hugo Loera Senior Technical Support Engineer.

Published byOlivia Willis Modified over 9 years ago

Similar presentations

Presentation on theme: "COMP-13: The “Weakest-Link” in your High Availability system How to make sure your HA is really highly available Hugo Loera Senior Technical Support Engineer."— Presentation transcript:

1 COMP-13: The “Weakest-Link” in your High Availability system How to make sure your HA is really highly available Hugo Loera Senior Technical Support Engineer

2 © 2007 Progress Software Corporation 2 COMP-13: The “Weakest-Link” in your High Availability system Goals  To consider the entire system architecture for High Availability (HA).  Provide a summary of all the fault tolerance features that provide HA.  To think of possible disaster scenarios.

3 © 2007 Progress Software Corporation 3 COMP-13: The “Weakest-Link” in your High Availability system Agenda  Your system chain  Keeping your hardware protected  Keeping your network connected  DB availability  Protecting WebSpeed ™ and AppServer ™ tiers  Sonic ™ fault tolerance features

4 © 2007 Progress Software Corporation 4 COMP-13: The “Weakest-Link” in your High Availability system Your system chain  The strength of a computer system is based on it’s weakest link, much like a chain.  Goal: to remove all of the single points of failure for an application. User Software Hardware Facilities Network

5 © 2007 Progress Software Corporation 5 COMP-13: The “Weakest-Link” in your High Availability system Your system chain System ComponentsRedundant Components Software ApplicationAdditional application tiers DatabaseClusters, Replication OSComputer cluster node Hardware NetworkAlternate network links Storage DevicesRedundant File Servers RAID, Remote data replication devices CPUClusters Power SourceUPS, Power Plant

6 © 2007 Progress Software Corporation 6 COMP-13: The “Weakest-Link” in your High Availability system Your system chain Application Servers  It is necessary to provide redundancy Data Base WebSpeed SonicMQ ® Hardware Facilities Sonic Adapters Sonic Adapters Internet Network Alternate site Name Server Fault Tolerance Clustered Servers Multiple links Multiple links CAA Multiple Web Servers SonicMQ ® Cluster & Replication Multiple WS Brokers Multiple WS Brokers Multiple ABL-Adapters Multiple ABL-Adapters

7 © 2007 Progress Software Corporation 7 COMP-13: The “Weakest-Link” in your High Availability system Agenda  Your system chain  Keeping your hardware protected  Keeping your network connected  DB availability  Protecting WebSpeed ™ and AppServer ™ tiers  Sonic fault tolerance features

8 © 2007 Progress Software Corporation 8 COMP-13: The “Weakest-Link” in your High Availability system Alternate site Clustered Servers Keeping your hardware protected

9 © 2007 Progress Software Corporation 9 COMP-13: The “Weakest-Link” in your High Availability system Keeping your hardware protected  Hardware Storage Devices –RAID, Remote data replication device CPU –Cluster hardware Facilities –Air conditioning –Fire and flood protection –Power Source  UPS, Power Plant, Alternative Power Supplies  Alternate site

10 © 2007 Progress Software Corporation 10 COMP-13: The “Weakest-Link” in your High Availability system RAID Configuration Keeping your hardware protected  RAID (redundant array of independent disks) Striping (provides load balancing) Mirrored configurations (for increased reliability) Fiber Channel

11 © 2007 Progress Software Corporation 11 COMP-13: The “Weakest-Link” in your High Availability system Node 1 Application OS Local Storage Cluster Manager Common Storage DB OE Enterpris e Cluster name or Cluster IP Address Node 2 Application OS Cluster Manager Local Storage OE Enterpris e Heartbeat Keeping your hardware protected  HA Cluster

12 © 2007 Progress Software Corporation 12 COMP-13: The “Weakest-Link” in your High Availability system Node 1 Application OS Local Storage Cluster Manager Common Storage DB OE Enterpris e Cluster name or Cluster IP Address Node 2 Application OS Cluster Manager Local Storage OE Enterpris e Keeping your hardware protected X Failover  Cluster

13 © 2007 Progress Software Corporation 13 COMP-13: The “Weakest-Link” in your High Availability system Agenda  Your system chain  Keeping your hardware protected  Keeping your network connected  DB availability  Protecting WebSpeed ™ and AppServer ™ tiers  Sonic fault tolerance features

14 © 2007 Progress Software Corporation 14 COMP-13: The “Weakest-Link” in your High Availability system Alternate site Clustered Servers Multiple links Multiple links Keeping your network connected

15 © 2007 Progress Software Corporation 15 COMP-13: The “Weakest-Link” in your High Availability system Keeping your network connected  Network Alternate network paths Redundant network links Configure a Domain Name Server (DNS) Site B Site A Users site

16 © 2007 Progress Software Corporation 16 COMP-13: The “Weakest-Link” in your High Availability system Keeping your network connected  If using alternate site Use a “virtual” DNS entry for –Your DB server –Application server –Web servers –Programs File Server Hostnames should be virtual names  Consider user VPN access for emergencies

17 © 2007 Progress Software Corporation 17 COMP-13: The “Weakest-Link” in your High Availability system Agenda  Your system chain  Keeping your hardware protected  Keeping your network connected  DB availability  Protecting WebSpeed ™ and AppServer ™ tiers  Sonic fault tolerance features

18 © 2007 Progress Software Corporation 18 COMP-13: The “Weakest-Link” in your High Availability system Alternate site Clustered Servers Cluster & Replication DB availability Multiple links Multiple links

19 © 2007 Progress Software Corporation 19 COMP-13: The “Weakest-Link” in your High Availability system DB availability  Cluster configuration Protects from hardware failure Quick recovery time Easy to register DB once the cluster has been configured.  OpenEdge ® cluster support Included with the Enterprise RDBMS Allows use of the procluster command to: –register the DB with the cluster manager –disable DB registration –start and stop the DB –query the status of the DB

20 © 2007 Progress Software Corporation 20 COMP-13: The “Weakest-Link” in your High Availability system  Vendor specific cluster commands DB availability

21 © 2007 Progress Software Corporation 21 COMP-13: The “Weakest-Link” in your High Availability system DB availability  OE provides a common interface For different cluster products. To integrate OE commands into the cluster environment...stop procluster DB stop pscluster Node 1 Cluster Manager OE Enterpris e Caa_sto p…

22 © 2007 Progress Software Corporation 22 COMP-13: The “Weakest-Link” in your High Availability system DB availability  OpenEdge DB replication Protects from storage problems Site fault tolerance protection Can be manually activated Source (live) Target Client Transition Failover Live Client X Transition Failback Target Live Client

23 © 2007 Progress Software Corporation 23 COMP-13: The “Weakest-Link” in your High Availability system DB availability Combining OpenEdge Replication with Clusters Node 1 DB Broker Operating System Cluster Manager Common Storage Local Storage OpenEdge Enterprise DB & Replication Node 2 Operating System Cluster Manager Local Storage OpenEdge Enterprise DB & Replication Target DB Replication Agent Replication Server OpenEdge Enterprise & Replication Source DB Site A Site B

24 © 2007 Progress Software Corporation 24 COMP-13: The “Weakest-Link” in your High Availability system Combining OpenEdge Replication with Clusters Node 1 Operating System Cluster Manager Common Storage Local Storage OpenEdge Enterprise DB & Replication Node 2 Operating System Cluster Manager Local Storage OpenEdge Enterprise DB & Replication Target DB Replication Agent Replication Server OpenEdge Enterprise & Replication Source DB Site A Site B DB Broker DB availability X

25 © 2007 Progress Software Corporation 25 COMP-13: The “Weakest-Link” in your High Availability system Combining OpenEdge Replication with Clusters Common Storage Node 2 Operating System Cluster Manager Local Storage OpenEdge Enterprise DB & Replication DB DB Broker OpenEdge Enterprise & Replication Source DB Site A Site B Node 1 Operating System Cluster Manager Local Storage OpenEdge Enterprise DB & Replication XXX DB availability X

26 © 2007 Progress Software Corporation 26 COMP-13: The “Weakest-Link” in your High Availability system Agenda  Your system chain  Keeping your hardware protected  Keeping your network connected  DB availability  Protecting WebSpeed ™ and AppServer ™ tiers  Sonic fault tolerance features

27 © 2007 Progress Software Corporation 27 COMP-13: The “Weakest-Link” in your High Availability system Alternate site Clustered Servers Multiple links Multiple links Cluster & Replication Protecting WebSpeed and AppServer tiers Name Server Fault Tolerance Multiple Web Servers Multiple WS Brokers Multiple WS Brokers Multiple ABL-Adapters Multiple ABL-Adapters

28 © 2007 Progress Software Corporation 28 COMP-13: The “Weakest-Link” in your High Availability system Protecting WebSpeed and AppServer tiers  NameServer Fault Tolerance Using UDP broadcast address Will provide instant access to alternate brokers Can use Name Server Load Balancing  Redundant brokers can be registered AppServer brokers WebSpeed brokers

29 © 2007 Progress Software Corporation 29 COMP-13: The “Weakest-Link” in your High Availability system Protecting WebSpeed and AppServer tiers  Name Server Replication based fault tolerance Client Host2 NS1 AppServer Broker WebSpeed Broker Subnet LAN 1 Gb Backbone Messenger WebServer INTERNET Host1 NS1 AppServer Broker WebSpeed Broker

30 © 2007 Progress Software Corporation 30 COMP-13: The “Weakest-Link” in your High Availability system  Getting the UDP broadcast address on UNIX $ netstat -i Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue lo0 8232 loopback localhost 2318894 0 42318894 0 0 le0 1500 psc-bed oasis 3625559 16 79807506 0 0 0 $ ifconfig le0 ce0: flags=1000843 mtu 1500 index 2 inet 192.128.5.30 netmask ffff0000 broadcast 192.128.255.255 Protecting WebSpeed and AppServer tiers

31 © 2007 Progress Software Corporation 31 COMP-13: The “Weakest-Link” in your High Availability system  Getting the UDP broadcast address on Windows C:\>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix. : blabla.speak.com IP Address............ : 192.128.3.24 Subnet Mask........... : 255.255.0.0 Default Gateway......... : 192.128.3.1 IP address 192.128. 3. 24 Subnet Mask 255.255. 0. 0 __________________ UDP Broadcast= IP address 192.128. 3. 24 NOT Subnet Mask 0. 0.255.255 OR __________________ UDP Broadcast= 192.128.255.255 Protecting WebSpeed and AppServer tiers

32 © 2007 Progress Software Corporation 32 COMP-13: The “Weakest-Link” in your High Availability system Connect(“-H 192.128.255.255 -S 5162 - AppService asbroker1”) NameServer=NS1 portNumber=5162 hostName=192.128.255.255 NAME SERVER REPLICATION Client Host2 NS1 AppServer Broker Subnet LAN Host1 NS1 AppServer Broker Protecting WebSpeed and AppServer tiers

33 © 2007 Progress Software Corporation 33 COMP-13: The “Weakest-Link” in your High Availability system Protecting WebSpeed and AppServer tiers  Using redundant WebSpeed brokers Messenger has to use UDP broadcast address Distributed standalone messengers can be configured Can use Name Server Load Balancing  Can use multiple web servers For fault tolerance Load balancing Multiple products are currently available for web server fault tolerance and load balancing

34 © 2007 Progress Software Corporation 34 COMP-13: The “Weakest-Link” in your High Availability system Protecting WebSpeed and AppServer tiers  Stand alone WebSpeed Messenger ubroker.properties configuration # # Sample definition of a NameServer # [NameServer.NS1] location=remote hostname=192.128.255.255 environment=NS1 srvrLogFile=$WRKDIR/NS1.ns.log autoStart=0. # # WebSpeed Messenger Properties # [WebSpeed.Messengers] certStorePath=$DLC/certs/ controllingNameServer=NS1

35 © 2007 Progress Software Corporation 35 COMP-13: The “Weakest-Link” in your High Availability system Messenger WebServer INTERNET Protecting WebSpeed and AppServer tiers  Name Server Replication based fault tolerance Host2 NS1 WebSpeed Broker Subnet LAN Messenger WebServer INTERNET Host1 NS1 WebSpeed Broker

36 © 2007 Progress Software Corporation 36 COMP-13: The “Weakest-Link” in your High Availability system ABL application working with SonicMQ OpenEdge Database Unified Broker OpenEdge ABL *.w, *.p ABL-JMS API ABL Adapter broker Sonic MQ Protecting WebSpeed and AppServer tiers

37 © 2007 Progress Software Corporation 37 COMP-13: The “Weakest-Link” in your High Availability system Agenda  Your system chain  Keeping your hardware protected  Keeping your network connected  DB availability  Protecting WebSpeed ™ and AppServer ™ tiers  Sonic fault tolerance features

38 © 2007 Progress Software Corporation 38 COMP-13: The “Weakest-Link” in your High Availability system Alternate site Name Server Fault Tolerance Clustered Servers Multiple links Multiple links Multiple Web Servers CAA SonicMQ ® Cluster & Replication Multiple WS Brokers Multiple WS Brokers Multiple ABL-Adapters Multiple ABL-Adapters Sonic fault tolerance features

39 © 2007 Progress Software Corporation 39 COMP-13: The “Weakest-Link” in your High Availability system Sonic fault tolerance features What is SonicMQ ® ?  A Standards-Based Enterprise Messaging Server  User benefits Uses standards-based infrastructure Enterprise-class reliability Configuration monitoring Can include message transformation and routing using ESB (Enterprise Service Bus).

40 © 2007 Progress Software Corporation 40 COMP-13: The “Weakest-Link” in your High Availability system Sonic Components  Domain Domain Manager –Agent Manager –Manager Broker –Directory Service  Containers MQ Container provides runtime support for Sonic components Can include ESB Containers to hosts ESB services  Messaging Nodes Message Broker Broker Cluster Sonic fault tolerance features Domain Container1 Queue Topic Container2 ESB Container Management Broker Agent Manager Directory Service Message Broker Queue Topic

41 © 2007 Progress Software Corporation 41 COMP-13: The “Weakest-Link” in your High Availability system Continuous Availability Architecture features  SonicMQ's CAA includes: Resilient client connections Replication brokers Fault tolerant management services and communications  Use some or all of these features to provide a continuously available messaging infrastructure. Sonic fault tolerance features

42 © 2007 Progress Software Corporation 42 COMP-13: The “Weakest-Link” in your High Availability system Resilient client connections JMS Client Lost connection Recovered connection Fault Tolerant Broker Broker preserves client context Fault tolerant client runtime preserves session Sonic fault tolerance features

43 © 2007 Progress Software Corporation 43 COMP-13: The “Weakest-Link” in your High Availability system Replicated Brokers  Creates a primary and backup broker  Backup broker replicates all acceptors on primary  Primary accepts clients and sends replications data to backup  Both brokers are functionally equivalent Sonic fault tolerance features

44 © 2007 Progress Software Corporation 44 COMP-13: The “Weakest-Link” in your High Availability system Replicated brokers Replication connection ping, ping, ping, … Broker DB JMS Client Broker (Standby) Broker (Active) Sonic fault tolerance features

45 © 2007 Progress Software Corporation 45 COMP-13: The “Weakest-Link” in your High Availability system Broker roles: failing over JMS Client Broker (new active) Lost connection Recovered connection Broker (formerly active) Replicated Broker pair Sonic fault tolerance features X X

46 © 2007 Progress Software Corporation 46 COMP-13: The “Weakest-Link” in your High Availability system Continuously available management communications  Options include: A cluster of management brokers Replicated management brokers Recommended Sonic fault tolerance features

47 © 2007 Progress Software Corporation 47 COMP-13: The “Weakest-Link” in your High Availability system Broker 1 Sonic fault tolerance features Domain ESB Container JMS Client Broker 2 Interbroker Connection Replicated brokers Broker Cluster Node Host B Host A

48 © 2007 Progress Software Corporation 48 COMP-13: The “Weakest-Link” in your High Availability system Continuously available management Container1 Broker1 (Backup) Container2 Agent Manager (Backup) Container3 Sonic fault tolerance features Agent Manager (Primary) Broker1 (Primary) Directory Service (Primary) Directory Service (Backup)

49 © 2007 Progress Software Corporation 49 COMP-13: The “Weakest-Link” in your High Availability system Example of a clustered management topology Shared directory store Management broker Agent Manager Directory Service Container1 Management broker Agent Manager Directory Service Container2 Cluster Primary Backup Management client Management client Management client Sonic fault tolerance features

50 © 2007 Progress Software Corporation 50 COMP-13: The “Weakest-Link” in your High Availability system Site B Site A The big picture

51 © 2007 Progress Software Corporation 51 COMP-13: The “Weakest-Link” in your High Availability system In Summary  Consider all possible components involved in the Application.  Make a plan that supports your HA configuration.  Progress products have all the required technology for HA.

52 © 2007 Progress Software Corporation 52 COMP-13: The “Weakest-Link” in your High Availability system For more Information, go to…  PSDN DB–12: Achieving High Availability with Clusters and OpenEdge Replication http://www.psdn.com/library/entry!default.jspa?categoryID=254& externalID=850 http://www.psdn.com/library/entry!default.jspa?categoryID=254& externalID=850 OpenEdge Replication How–To http://www.psdn.com/library/entry!default.jspa?categoryID=254& externalID=841 http://www.psdn.com/library/entry!default.jspa?categoryID=254& externalID=841 Messaging Fundamentals for Sonic ESB http://www.psdn.com/library/entry!default.jspa?categoryID=91&e xternalID=2143 http://www.psdn.com/library/entry!default.jspa?categoryID=91&e xternalID=2143  Documentation: Open Edge 10.1B Installation and Configuration Guide OpenEdge Getting Started: Application and Integration Services Progress SonicMQ Deployment Guide V7.5

53 © 2007 Progress Software Corporation 53 COMP-13: The “Weakest-Link” in your High Availability system Questions?

54 © 2007 Progress Software Corporation 54 COMP-13: The “Weakest-Link” in your High Availability system Thank you for your time

55 © 2007 Progress Software Corporation 55 COMP-13: The “Weakest-Link” in your High Availability system

Download ppt "COMP-13: The “Weakest-Link” in your High Availability system How to make sure your HA is really highly available Hugo Loera Senior Technical Support Engineer."

Similar presentations

Module 13: Implementing ISA Server 2004 Enterprise Edition: Site-to-Site VPN Scenario.

Module 13: Implementing ISA Server 2004 Enterprise Edition: Site-to-Site VPN Scenario.
Chapter 5: Server Hardware and Availability. Hardware Reliability and LAN The more reliable a component, the more expensive it is. Server hardware is.

Chapter 5: Server Hardware and Availability. Hardware Reliability and LAN The more reliable a component, the more expensive it is. Server hardware is.
OPS-7: Migrating your Distributed Application from V9 to OpenEdge ® 10 with (Almost) No Downtime Roy Ellis Principal QA Engineer.

OPS-7: Migrating your Distributed Application from V9 to OpenEdge ® 10 with (Almost) No Downtime Roy Ellis Principal QA Engineer.
MCTS Guide to Microsoft Windows Server 2008 Network Infrastructure Configuration Chapter 4 Installing and Configuring the Dynamic Host Configuration Protocol.

MCTS Guide to Microsoft Windows Server 2008 Network Infrastructure Configuration Chapter 4 Installing and Configuring the Dynamic Host Configuration Protocol.
June 23rd, 2009Inflectra Proprietary InformationPage: 1 SpiraTest/Plan/Team Deployment Considerations How to deploy for high-availability and strategies.

June 23rd, 2009Inflectra Proprietary InformationPage: 1 SpiraTest/Plan/Team Deployment Considerations How to deploy for high-availability and strategies.
1 © Copyright 2010 EMC Corporation. All rights reserved. EMC RecoverPoint/Cluster Enabler for Microsoft Failover Cluster.

1 © Copyright 2010 EMC Corporation. All rights reserved. EMC RecoverPoint/Cluster Enabler for Microsoft Failover Cluster.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 1: Introduction to Windows Server 2003.

70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 1: Introduction to Windows Server 2003.
Lesson 1: Configuring Network Load Balancing

Lesson 1: Configuring Network Load Balancing
1© Copyright 2011 EMC Corporation. All rights reserved. EMC RECOVERPOINT/ CLUSTER ENABLER FOR MICROSOFT FAILOVER CLUSTER.

1© Copyright 2011 EMC Corporation. All rights reserved. EMC RECOVERPOINT/ CLUSTER ENABLER FOR MICROSOFT FAILOVER CLUSTER.
Implementing Failover Clustering with Hyper-V

Implementing Failover Clustering with Hyper-V
Virtual Network Servers. What is a Server? 1. A software application that provides a specific one or more services to other computers  Example: Apache.

Virtual Network Servers. What is a Server? 1. A software application that provides a specific one or more services to other computers  Example: Apache.
11 SERVER CLUSTERING Chapter 6. Chapter 6: SERVER CLUSTERING2 OVERVIEW  List the types of server clusters.  Determine which type of cluster to use for.

11 SERVER CLUSTERING Chapter 6. Chapter 6: SERVER CLUSTERING2 OVERVIEW  List the types of server clusters.  Determine which type of cluster to use for.
Implementing High Availability

Implementing High Availability
MCTS Guide to Microsoft Windows Server 2008 Applications Infrastructure Configuration (Exam # 70-643) Chapter Ten Configuring Windows Server 2008 for High.

MCTS Guide to Microsoft Windows Server 2008 Applications Infrastructure Configuration (Exam # ) Chapter Ten Configuring Windows Server 2008 for High.
Microsoft Load Balancing and Clustering. Outline Introduction Load balancing Clustering.

Microsoft Load Balancing and Clustering. Outline Introduction Load balancing Clustering.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 1: Introduction to Windows Server 2003.

70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 1: Introduction to Windows Server 2003.
Microsoft ® Application Virtualization 4.6 Infrastructure Planning and Design Published: September 2008 Updated: February 2010.

Microsoft ® Application Virtualization 4.6 Infrastructure Planning and Design Published: September 2008 Updated: February 2010.
Computerized Networking of HIV Providers Networking Fundamentals Presented by: Tom Lang – LCG Technologies Corp. May 8, 2003.

Computerized Networking of HIV Providers Networking Fundamentals Presented by: Tom Lang – LCG Technologies Corp. May 8, 2003.
SX.enterprise Architecture & Deployment Session #24 Duc Chu & Perry Jager.

SX.enterprise Architecture & Deployment Session #24 Duc Chu & Perry Jager.
DB-12: Achieving High Availability with Clusters and OpenEdge® Replication Combining the two technologies Hugo Loera Chávez Senior Tech Support Engineer.

DB-12: Achieving High Availability with Clusters and OpenEdge® Replication Combining the two technologies Hugo Loera Chávez Senior Tech Support Engineer.

Similar presentations

Ads by Google