OPS-13: Building and Deploying a Highly Available Application Brian Bowman Sr. Solution Engineer.

Slides:



Advertisements
Similar presentations
Intro to SharePoint 2013 Architecture Liam Cleary.
Advertisements

Business Continuity Section 3(chapter 8) BC:ISMDR:BEIT:VIII:chap8:Madhu N PIIT1.
OPS-21: Managing Multiple Sites Part Time: Replication & OpenEdge ® Management Case Study Brian Bowman Sr Solution Engineer.
OPS-10: Managing multiple sites part time: Replication & OpenEdge Management Case Study Brian Bowman Sr. Solution Engineer.
© 2009 EMC Corporation. All rights reserved. Introduction to Business Continuity Module 3.1.
High Availability 24 hours a day, 7 days a week, 365 days a year… Vik Nagjee Product Manager, Core Technologies InterSystems Corporation.
1 Disk Based Disaster Recovery & Data Replication Solutions Gavin Cole Storage Consultant SEE.
OPS-7: Migrating your Distributed Application from V9 to OpenEdge ® 10 with (Almost) No Downtime Roy Ellis Principal QA Engineer.
Scale Up Access to your 4GL Application using Web Services
2 June 2015 © Enterprise Storage Group, Inc. 1 The Case for File Server Consolidation using NAS Nancy Marrone Senior Analyst The Enterprise Storage Group,
Microsoft Virtual Server 2005 Product Overview Mikael Nyström – TrueSec AB MVP Windows Server – Setup/Deployment Mikael Nyström – TrueSec AB MVP Windows.
SQL Server 2012 Always On Premier Field Engineer Microsoft Corporation Lisa Gardner
1© Copyright 2012 EMC Corporation. All rights reserved. November 2013 Oracle Continuous Availability – Technical Overview.
SharePoint Business Continuity Management with SQL Server AlwaysOn
John Graham – STRATEGIC Information Group Steve Lamb - QAD Disaster Recovery Planning MMUG Spring 2013 March 19, 2013 Cleveland, OH 03/19/2013MMUG Cleveland.
Is Windows Right for High-Availability Enterprise Applications? Dan Kusnetzky, Vice President System Software Research IDC.
How WebMD Maintains Operational Flexibility with NoSQL Rajeev Borborah, Sr. Director, Engineering Matt Wilson – Director, Production Engineering – Consumer.
DB-12: Achieving High Availability with Clusters and OpenEdge® Replication Combining the two technologies Hugo Loera Chávez Senior Tech Support Engineer.
STEALTH Content Store for SharePoint using Windows Azure  Boosting your SharePoint to the MAX! "Optimizing your Business behind the scenes"
Treasury in the Cloud Bob Stark – Vice President, Strategy September 17, 2014.
Cloud Computing for the Enterprise November 18th, This work is licensed under a Creative Commons.
Database Architectures and the Web
Database Services for Physics at CERN with Oracle 10g RAC HEPiX - April 4th 2006, Rome Luca Canali, CERN.
CIS 325: Data Communications1 CIS-325 Data Communications Dr. L. G. Williams, Instructor.
DONE-10: Adminserver Survival Tips Brian Bowman Product Manager, Data Management Group.
Business Continuity and Disaster Recovery Chapter 8 Part 2 Pages 914 to 945.
1 Progress Software’s OpenEdge Platform Which database is right for your environment? Simon Epps.
© Novell, Inc. All rights reserved. 1 PlateSpin Protect Virtualize your Disaster Recovery.
Networked Application Architecture Design. Application Building Blocks Application Software Data Infrastructure Software Local Area Network Server Desktop.
STEALTH Content Store for SharePoint using Caringo CAStor  Boosting your SharePoint to the MAX! "Optimizing your Business behind the scenes"
Sofia, Bulgaria | 9-10 October SQL Server 2005 High Availability for developers Vladimir Tchalkov Crossroad Ltd. Vladimir Tchalkov Crossroad Ltd.
IT Infrastructure Chap 1: Definition
Introduction to Cloud Computing
ArcGIS for Server: Reference Implementations
PaaS for the Modern Web A powerful self service platform for developers A flexible hosting solution for IT Web Sites for Windows Server Scalable Scale.
Cloud Computing & Amazon Web Services – EC2 Arpita Patel Software Engineer.
DB-2: OpenEdge® Replication: How to get Home in Time … Brian Bowman Sr. Solutions Engineer Sandy Caiado Sr. Solutions Engineer.
Chapter © 2006 The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/ Irwin Chapter 7 IT INFRASTRUCTURES Business-Driven Technologies 7.
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.
SOA-14: Deploying your SOA Application David Cleary Principal Software Engineer.
Designing a Scalable Enterprise Project Management Architecture Ken Toole Platform Test Manager MS Project Microsoft Corporation.
© Copyright IBM Corporation 2013 June 2013 IBM Integrated System Test Page 1 IBM Integrated Solutions Test Enterprise Test Series: Ideal Stack Testing.
SONIC-3: Creating Large Scale Installations & Deployments Andrew S. Neumann Principal Engineer, Progress Sonic.
SOA-02: Sonic SOA Products Overview Luis Maldonado Technical Product Manager Sonic Software.
B8: Building and Deploying a Highly Available Application David Eddy Senior Solution Consultant.
SOA-9: Implementing SOA in Financial Services Banco Comafi a Real Leading Case Hernan Aymard Sr Solution Architect Javier Betancourt Sr. Project Manager.
OSIsoft High Availability PI Replication
INNOV-02 Integrating your Business Logic with the World Jan Van Lishout - Tom Vanpol Progress Software.
SONIC-3: Creating Large Scale Installations & Deployments Andrew S. Neumann Principal Engineer Progress Sonic.
High Availability in DB2 Nishant Sinha
Joe D’Angelo, Sr. Systems Engineer Serverware Corp.
CERN - IT Department CH-1211 Genève 23 Switzerland t High Availability Databases based on Oracle 10g RAC on Linux WLCG Tier2 Tutorials, CERN,
Data Communications and Networks Chapter 9 – Distributed Systems ICT-BVF8.1- Data Communications and Network Trainer: Dr. Abbes Sebihi.
Enhancing Scalability and Availability of the Microsoft Application Platform Damir Bersinic Ruth Morton IT Pro Advisor Microsoft Canada
United SWE, Inc. Quality endorsement a presentation of our capabilities.
Narasimha Reddy Gopu Jisha J. Agenda Introduction to AlwaysOn * AlwaysOn Availability Groups (AG) & Listener * AlwaysOn Failover * AlwaysOn Active Secondaries.
가상화 기반의 Workload 관리솔루션 : FORGE PlateSpin Virtualization and Workload Management 나영관 한국노벨 /
2 Copyright © Oracle Corporation, All rights reserved. Basic Oracle Net Architecture.
Disaster Recovery Prepared by Mark Lomas Mark Lomas IT Infrastructure Consultant Storage & Servers.
OSIsoft High Availability PI Replication Colin Breck, PI Server Team Dave Oda, PI SDK Team.
Database recovery contd…
Business System Development
Adam Backman Chief Cat Wrangler – White Star Software
High Availability 24 hours a day, 7 days a week, 365 days a year…
Disaster Recovery Services
Microsoft Ignite NZ October 2016 SKYCITY, Auckland.
Comparison June 2017.
Minimize Unplanned Downtime and Data Loss with OpenEdge
Using the Cloud for Backup, Archiving & Disaster Recovery
OPS-7: Building and Deploying a Highly Available Application
Presentation transcript:

OPS-13: Building and Deploying a Highly Available Application Brian Bowman Sr. Solution Engineer

© 2008 Progress Software Corporation2 OPS-13: Building & Deploying a Highly Available Application What part is the most important?

© 2008 Progress Software Corporation3 OPS-13: Building & Deploying a Highly Available Application Agenda  Highly Available Application (HAA) – what it means today & tomorrow  Definitions  Levels of Recovery

© 2008 Progress Software Corporation4 OPS-13: Building & Deploying a Highly Available Application HAA – What is it?  Ensuring the complete application is 100% available during the required business time  Meeting Business Needs Recovery Time Objective (RTO) Recovery Point Objective (RPO)  Eliminating all Single Point of Failures (SPF)  Including as many TLA’s as possible in one presentation… (TLA = Three Letter Acronyms)

© 2008 Progress Software Corporation5 OPS-13: Building & Deploying a Highly Available Application Where does a Highly Available Application start?  Development DevelopmentDeploymentManagement Application development & deployment timeline  Deployment  Management

© 2008 Progress Software Corporation6 OPS-13: Building & Deploying a Highly Available Application Where does a Highly Available Application start? DevelopmentDeploymentManagement Application development & deployment timeline

© 2008 Progress Software Corporation7 OPS-13: Building & Deploying a Highly Available Application What does a HAA look like to the user?  The application is always available*  Performance is always acceptable  Data is NEVER lost  New functionality is timely

© 2008 Progress Software Corporation8 OPS-13: Building & Deploying a Highly Available Application Definitions: High Availability (HA) “… high availability refers to a system or component that is continuously operational for a desirably long length of time. Availability can be measured relative to "100% operational" or "never failing." A widely-held but difficult-to-achieve standard of availability for a system or product is known as "five 9s" ( percent)...” ReliabilityOK For Expected Outages/Year Three 9's99.9%Homes9 hours Four 9's99.99%Factories59 minutes Five 9's99.999%Hospitals5 minutes Six 9's %Banks32 seconds Seven 9's %Digital Markets30 msec (Source: (Source:

© 2008 Progress Software Corporation9 OPS-13: Building & Deploying a Highly Available Application Agenda  Highly Available Application ( HAA) – what it means today & tomorrow  Definitions  Levels of Recovery

© 2008 Progress Software Corporation10 OPS-13: Building & Deploying a Highly Available Application Definitions: Complete Application  User Interface  Middleware (Application Server / Sonic ™ )  Data (database)  Common Infrastructure Presentation Business Services Data Access Data Sources Common Infrastructure Enterprise Services

© 2008 Progress Software Corporation11 OPS-13: Building & Deploying a Highly Available Application Definitions: Complete Application An Example  User Interface  Middleware (Application Server / Sonic)  Data (database) User Interface Application Server Data Access Databases Operations / HW ESB

© 2008 Progress Software Corporation12 OPS-13: Building & Deploying a Highly Available Application Definitions: The Example Application  4 Application Configurations Hosted (single server) Client Server N-Tier SaaS User Interface Application Server Databases Ops / HW ESB

© 2008 Progress Software Corporation13 OPS-13: Building & Deploying a Highly Available Application Logical vs. Physical Outlook AS DB AS Web Svr WS DB AS Web Svr WS AS WS Client / Server N-Tier SaaS Hosted (Single Server)

© 2008 Progress Software Corporation14 OPS-13: Building & Deploying a Highly Available Application Agenda  Highly Available Application ( HAA) – what it means today & tomorrow  Definitions  Levels of Recovery

© 2008 Progress Software Corporation15 OPS-13: Building & Deploying a Highly Available Application Levels of Recovery Level 1: Bicycle Recovery Level 2: VW Recovery Level 3: Race Car Recovery

© 2008 Progress Software Corporation16 OPS-13: Building & Deploying a Highly Available Application Level 1: Business Case  Easiest environment to work in  RTO and RPO < 1 day  Typically Host-based Client-Server  Development left to the Application Partner (usually) Cost Scale:

© 2008 Progress Software Corporation17 OPS-13: Building & Deploying a Highly Available Application Level 1: Technology Dependence  NO RPO or RTO  Have never had an incident  Not using their existing resources  Don’t rely completely on technology!

© 2008 Progress Software Corporation18 OPS-13: Building & Deploying a Highly Available Application Level 1: Technology Choices  Backup Infrastructure –Hardware –Software Application –Configuration files –Properties files  Where is your recovery location?

© 2008 Progress Software Corporation19 OPS-13: Building & Deploying a Highly Available Application Level 2: Business case  RTO and RPO < 60 minutes  Typically Host-based Client-server N-tier  Development shared between AP and User  Deployment shared as well Cost Scale:

© 2008 Progress Software Corporation20 OPS-13: Building & Deploying a Highly Available Application Level 2: Choosing The Right Tool Which tool would you choose…

© 2008 Progress Software Corporation21 OPS-13: Building & Deploying a Highly Available Application Level 2: Technology Choices  After imaging  Replication or clusters  SAN solutions  Recovery offsite?

© 2008 Progress Software Corporation22 OPS-13: Building & Deploying a Highly Available Application Level 3: Business Case  RTO and RPO < 5 minutes  Typically All Deployment Models (Host-based, Client- server, N-tier, SaaS)  Real-time and near real-time  Large development organization  Deployment important (and difficult) Cost Scale:

© 2008 Progress Software Corporation23 OPS-13: Building & Deploying a Highly Available Application Level 3: Thinking Ahead Of The Game  Rick Mears 4 Time Indianapolis 500 winner 6 Times – Poll position 11 Times – Front row

© 2008 Progress Software Corporation24 OPS-13: Building & Deploying a Highly Available Application Level 3: Technology Choices  Replication  Clusters  SAN solution with complete redundancy  Sonic ESB / CAA

© 2008 Progress Software Corporation25 OPS-13: Building & Deploying a Highly Available Application Backup (Site 2) OpenEdge Replication Application Server (Site 2) Web Server Name Server (Load balancing) Client Application Server (Site 1) Reporting Name Server (Load balancing) Production (Site 1) User Interface Application Server Tier Data Tier Direct Connect TCP/IP SQL Level 3: Technology Choices: Application Availability – eliminating SPFs Client Enterprise Services

© 2008 Progress Software Corporation26 OPS-13: Building & Deploying a Highly Available Application Level 3: Technology Choices: Sonic CAA Q2 Q1 Q2a Q1a

© 2008 Progress Software Corporation27 OPS-13: Building & Deploying a Highly Available Application Web Server Name Server (Load balancing) Client Application Server (Site 1) Application Server (Site 2) Reporting Backup (Site 2) Name Server (Load balancing) Production (Site 1) User Interface Application Server Tier Data Tier Direct Connect TCP/IP OpenEdge Replication SQL Level 3: Technology Choices: SaaS – Same Rules Apply except Web Server Client Enterprise Services

© 2008 Progress Software Corporation28 OPS-13: Building & Deploying a Highly Available Application Wrap-up Recovery Level Business Requirements Technology Requirements 1< One DayBackup of complete system(s) Utilize exiting tools Dev & Depl not critical (mostly done by AP) All architectures apply 2< 60 MinutesDuplicate HW – Available and loaded Some existing and possibly new tools Dev shared, Depl & Maint. in-house All architectures apply 3< 5 MinutesComplete Redundancy (total HA) Advanced tools required Complete cycle critical (Dev, Depl, Maint.) All architectures apply

© 2008 Progress Software Corporation29 OPS-13: Building & Deploying a Highly Available Application Summary  Business Requirements are critical!  Different Architectures Levels of recovery Business Requirements Solutions  It is the complete process Development, Deployment, Maintenance

© 2008 Progress Software Corporation30 OPS-13: Building & Deploying a Highly Available Application For More Information  Sonic CAA  OpenEdge Reference Architecture  Disaster Recovery Resources reparedness_a_step_in_the_right_direction/index.html

© 2008 Progress Software Corporation31 OPS-13: Building & Deploying a Highly Available Application Questions ?

© 2008 Progress Software Corporation32 OPS-13: Building & Deploying a Highly Available Application Thank You

© 2008 Progress Software Corporation33 OPS-13: Building & Deploying a Highly Available Application