Download
slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Reach Your Technical Peak 2004 PowerPoint Presentation
Download Presentation
Reach Your Technical Peak 2004

Reach Your Technical Peak 2004

335 Vues Download Presentation
Télécharger la présentation

Reach Your Technical Peak 2004

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Reach Your Technical Peak 2004

  2. Business Continuity in the Progress Environment

  3. Agenda • Introduction • Evaluating the Risks • Planning • Implementation • Tools to Help • Summary

  4. Does this look familiar?

  5. “Business Continuity / Disaster Recovery was the #1 concern of data center executives.” June 2004 Survey Gartner, Inc.

  6. What is Disaster Recovery? • Definitive plan accepted by ALL levels of management • MUST be utilized when all other recovery measures have failed • Effective DR solution is a part of a HA requirements • Final stage of any HA solution

  7. The Availability Index *Adapted from Blueprints for High Availability by Evan Marcus and Hal Stern (ISBN: 0-471-43026-9)

  8. What do you need to Consider? • Insure the safety and security of employees • Fully equipped off-site facility • Ability to effectively run business from off-site facility

  9. Agenda • Introduction • Evaluating the Risks • Planning • Implementation • Tools to Help • Summary

  10. Too Much Caffeine?

  11. Evaluating the Risks "Half of U.S. corporations rate their internet downtime costs at more than $1,000 per hour." Yankee Group (http://www.yankeegroup.com)

  12. Evaluating the RisksCauses of Unplanned Downtime *Adapted from Blueprints for High Availability by Evan Marcus and Hal Stern (ISBN: 0-471-43026-9)

  13. Evaluating the RisksOther Considerations • Business process failure • Asset loss • Regulatory liability • Customer service failure • Damage to reputation or brand

  14. Agenda • Introduction • Evaluating the Risks • Planning • Implementation • Tools to Help • Summary

  15. Is this good planning?

  16. Planning "Power outages interrupt operations at 72 percent of U.S. businesses." Contingency Planning & Management Online (http://www.ContingencyPlanning.com) Ernst & Young (http://www.ey.com)

  17. Planning Questions to ask yourself • Do I need 99.999% availability? • How is this achieved? • Can I do more with what I already have? • What is my disaster recovery plan? • Do I need redundant systems? • Do I need redundant data? • Can the business continue in an off-line or manual mode?

  18. PlanningFreshness vs. Downtime Backup Refresh “Freshness” mths wks days hrs mins secs Recovery Time “Downtime” Zero secs hrs mins days wks mths Acceptable Downtime ? Recovery Time and Data Integrity “I’m up and running in seconds, but I’ve lost a day’s data” What Are My Disaster Recovery Needs? “I lost no data but it took me a weekto do it”

  19. PlanningCalculating the Value of Down Time • How much will this cost the enterprise in immediate and future loss of business? • How will this failure affect the corporate image? • Will the customer impact be only temporary or will customers leave forever? http://www.sss.co.nz/services/downtimepage.htm

  20. PlanningWhat do you have to consider • Database the easiest to think of • Complete OpenEdge Environment • Hardware • 3rd party Software • The application?

  21. Agenda • Introduction • Evaluating the Risks • Planning • Implementation • Tools to help you • Summary

  22. Implementing the Plan Combination of Resources Designed to withstand any single failure

  23. Implementing the Plan – Test • You should test your plan periodically (Not when you actually have to use it!!!) • Everyone that has responsibility in the plan has to participate! • How often should you test?

  24. Agenda • Introduction • Evaluating the Risks • Planning • Implementation • Tools to Help • Summary

  25. Business Continuity SolutionsTools to help you solve the problem… The OpenEdge Environment

  26. Fathom Management • Talked about it at previous Tech Peaks • Monitors the system • Puts procedures in place to help prevent a disaster • Puts procedures in place to lessen a disaster • Helps you plan for moving forward

  27. Fathom Replication • To prevent data loss from your database in the event of a hardware failure. • To provide a secondary reporting area to offload processing from the production machine • To guarantee business continuity continues in the event of a disaster

  28. Fathom Replication

  29. Fathom ReplicationComplete Configuration Source Database Target Database AI Extents Database Broker Processes Database Broker Processes Repl Queue Repl Server Repl Agent Repl Queue

  30. Fathom Replication Server Details • Configures and manages remote agents • Sends all database activity to its replication agents • Controls replication agents Source Database AI Extents Database Broker Processes Repl Server Repl Queue

  31. Fathom Replication Agent Details • Receives database activity from replication server • Performs continuous roll-forward to target database • Types of Agents • Asynchronous • Synchronous Target Database Database Broker Processes Repl Queue Repl Agent

  32. Fathom ReplicationWhat Happens If… Ouch! Bam Source Database Target Database AI Extents Database Broker Processes Database Broker Processes Repl Queue Repl Server Repl Agent Pow Repl Queue

  33. Fathom ReplicationWhat is a Failure? • Process terminates abnormally • Database crash • TCP/IP communications problem More important – how do we recover?

  34. Fathom ReplicationServer Failure Recovery Reconnect Attempt to Reconnect to Agent yes Perform Recovery Synchronization no no Timeout Expired Resume Normal Operation Connect timeout yes Another Agent yes Deactivate Failing Agent no Exit

  35. Fathom ReplicationAgent Failure Recovery Reconnect Listen for Server Connection yes Perform Recovery Synchronization no Timeout Expired no Resume Normal Operation Transition timeout yes Manual Transition Auto Transition yes Production Database no yes

  36. Fathom Replication “The main reason for [Replication] is the importance of the application to our business.” – Denise MacDonald, Network and Support Manager,Caledonian MacBrayne

  37. Agenda • Introduction • Evaluating the Risks • Planning • Implementation • Tools to Help • Summary

  38. Summary • Disaster Recovery is only part of High Availability • Fathom Management & Replication can help, but it is not the complete solution • Understand what your requirements are • Plan with those requirements in mind • Can you afford not to have a plan?