2. B8: Building and Deploying a Highly Available Application David Eddy Senior Solution Consultant

3. © 2008 Progress Software Corporation 2 What part is the most important?

4. © 2008 Progress Software Corporation 3 Agenda  Highly Available Application (HAA) – what it means today & tomorrow  Definitions  Levels of Recovery

5. © 2008 Progress Software Corporation 4 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)

6. © 2008 Progress Software Corporation 5 Where does a Highly Available Application start?  Development DevelopmentDeploymentManagement Application development & deployment timeline  Deployment  Management

7. © 2008 Progress Software Corporation 6 Where does a Highly Available Application start? DevelopmentDeploymentManagement Application development & deployment timeline

8. © 2008 Progress Software Corporation 7 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

9. © 2008 Progress Software Corporation 8 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" (99.999 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's99.9999%Banks32 seconds Seven 9's99.99999%Digital Markets30 msec (Source: http://searchdatacenter.techtarget.com/sDefinition/0,,sid80_gci761219,00.html#)http://searchdatacenter.techtarget.com/sDefinition/0,,sid80_gci761219,00.html# (Source: http://www.cps-corp.net/9s.htm)http://www.cps-corp.net/9s.htm

10. © 2008 Progress Software Corporation 9 Agenda  Highly Available Application ( HAA) – what it means today & tomorrow  Definitions  Levels of Recovery

11. © 2008 Progress Software Corporation 10 Definitions: Complete Application  User Interface  Middleware (Application Server / Sonic ™ )  Data (database)  Common Infrastructure Presentation Business Services Data Access Data Sources Common Infrastructure Enterprise Services

12. © 2008 Progress Software Corporation 11 Definitions: Complete Application An Example  User Interface  Middleware (Application Server / Sonic)  Data (database) User Interface Application Server Data Access Databases Operations / HW ESB

13. © 2008 Progress Software Corporation 12 Definitions: The Example Application  4 Application Configurations Hosted (single server) Client Server N-Tier SaaS User Interface Application Server Databases Ops / HW ESB

14. © 2008 Progress Software Corporation 13 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)

15. © 2008 Progress Software Corporation 14 Agenda  Highly Available Application ( HAA) – what it means today & tomorrow  Definitions  Levels of Recovery

16. © 2008 Progress Software Corporation 15 Levels of Recovery Level 1: Bicycle Recovery Level 2: VW Recovery Level 3: Race Car Recovery

17. © 2008 Progress Software Corporation 16 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:

18. © 2008 Progress Software Corporation 17 Level 1: Technology Dependence  NO RPO or RTO  Have never had an incident  Not using their existing resources  Don’t rely completely on technology!

19. © 2008 Progress Software Corporation 18 Level 1: Technology Choices  Backup Infrastructure –Hardware –Software Application –Configuration files –Properties files  Where is your recovery location?

20. © 2008 Progress Software Corporation 19 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:

21. © 2008 Progress Software Corporation 20 Level 2: Choosing The Right Tool Which tool would you choose…

22. © 2008 Progress Software Corporation 21 Level 2: Technology Choices  After imaging  Replication or clusters  SAN solutions  Recovery offsite?

23. © 2008 Progress Software Corporation 22 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:

24. © 2008 Progress Software Corporation 23 Level 3: Thinking Ahead Of The Game  Rick Mears 4 Time Indianapolis 500 winner 6 Times – Poll position 11 Times – Front row

25. © 2008 Progress Software Corporation 24 Level 3: Technology Choices  Replication  Clusters  SAN solution with complete redundancy  Sonic ESB / CAA

26. © 2008 Progress Software Corporation 25 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

27. © 2008 Progress Software Corporation 26 Level 3: Technology Choices: Sonic CAA Q2 Q1 Q2a Q1a

28. © 2008 Progress Software Corporation 27 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

29. © 2008 Progress Software Corporation 28 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

30. © 2008 Progress Software Corporation 29 Summary  Business Requirements are critical!  Different Architectures Levels of recovery Business Requirements Solutions  It is the complete process Development, Deployment, Maintenance

31. © 2008 Progress Software Corporation 30 For More Information  Sonic CAA http://www.psdn.com  OpenEdge Reference Architecture http://www.psdn.com/library/kbcategory.jspa?categoryID=230  Disaster Recovery Resources http://www.attanium.net http://www.redorbit.com/news/technology/507076/uk_emergency_p reparedness_a_step_in_the_right_direction/index.html http://www.emdat.be

32. © 2008 Progress Software Corporation 31 Questions ?

33. © 2008 Progress Software Corporation 32 Thank You

34. © 2008 Progress Software Corporation 33