Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Hybrid DR in the Cloud - Harford SIM 2015


Published on

A solid continuity solution begins with well-defined goals and success criteria. The technology to get the job done falls into place after that, but usually requires a blend of tools and techniques to get there. This is the presentation I delivered at the 2015 SIM event in Hartford, CT

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Hybrid DR in the Cloud - Harford SIM 2015

  1. 1. The Dream “Send it to the cloud!” • Recover to someone else’s infrastructure • Only pay for what you use, when you use it!
  2. 2. The Harsh Reality • Operational Impact o Who will be providing the daily care and feeding of the DR solution? • Consistency o Configuration Drift o Does your IT staff need to now make changes in 2 places for every move in production? • Costs o Is the solution a Ferrari? Ford? Fiero? o What does it actually cost to declare? Do you know?
  3. 3. The Challenge: Complexity  Lots of VMs…  Lots of storage…  Intricate WAN topology…  Physical appliances…  Mainframes…  Users need access to input data…
  4. 4. Goals for this Talk Learn common BCP pitfalls Strategies to focus your continuity planning Streamline your needs analysis Map tools and techniques to meet those needs best
  5. 5. Why listen to me? • Solutions Architect at TierPoint • I design managed DR and IaaS solutions every day • I talk to all walks of IT, across many verticals o People who have implemented their own solutions o What’s working? What’s not? o Where’s the mind share?
  6. 6. Common Mistakes in Business Continuity Planning
  7. 7. 6 Common Blunders 1. Picking a product or solution before defining requirements fully 2. Designing and pricing solutions before talking to your internal stakeholders 3. Designing for the “check-box” rather than function 4. Neglecting to test regularly 5. Neglecting to test fail-back 6. Settling for less because of past experiences
  8. 8. Boring…. “I just spun up 10 AWS instances while you talked. I’m in the cloud already!” • You feel like you’ve just made PROGRESS… • …but how does it address your project’s Success Criteria?
  9. 9. Your DR/BCP Journey Starts Here
  10. 10. Solution Stage Plan
  11. 11. Fundamental Drivers of IT BCP Solution RTOs & RPOs People Apps
  12. 12. Confer with Internal Stakeholders
  13. 13. Needs Analysis Process Conduct BIA Define RTOs/RPOs Establish Distance Requirements What’s the 1-3 Year IT Roadmap? Your Needs
  14. 14. BIA Worksheet Source
  15. 15. What are your priorities?  How up to date must the data be? (RPO)  How quickly must it be made available? (RTO)  Can employees/clients access the data?  How near or far must this be from [critical site] ?  What operational overhead does this create for my team?  How does the cost of DR align with changes to production? Is it predictable?  Can I live with a subset of production running at declaration time?  Does DR need to have full performance capabilities of production?
  16. 16. Collect and Aggregate Your Data
  17. 17. Solution Stage Plan Collect
  18. 18. Aggregate Your Data System Inventory Network Diagram Data Flow Diagram Network Utilization Backup Metrics Key People
  19. 19. Mapping Needs To a Solution
  20. 20. Solution Stage Plan Collect Map
  21. 21. Solution Approach 1. Easy Wins – native replication or clustering 2. RTOs & RPOs 3. VMs – what can be protected as a portable unit? 4. Physicals 1. Are any pending virtualization? 2. Does it support recovering into a VM? 3. Does it require a matching physical system? 5. Networking 1. What carriers are required? 2. What does the data change rate look like? 6. “Where are the eyeballs?” 1. Is workspace needed to ensure consistent data flow? 7. Security 1. What frameworks must be adhered to?
  22. 22. RTO/RPO Technology Drivers Configure hardware (p or v) Install OS Configure OS Install backup agent Start recovery Restore VM Power on VM Backup & Recovery 24+ hr RTO; 24 hr RPO < 1-4 hr RTO; ~0-15min RPO Replication Load Balanced High Availability ~0 hr RTO, ~0 hr RPO
  23. 23. Solution Map
  24. 24. DR Responsibility Matrix Process Client Provider DR Declaration Primary Replication Health Primary Backup Success Primary DR Testing Primary Assist DR Runbook Assist Primary DR Infrastructure Primary
  25. 25. Bringing it all together
  26. 26. Hybrid Cloud DR Infrastructure Continuity Approach • Colocation • Cloud o Private o Public • Managed Hosting • Workspace Recovery • High-Availability • Replication o VM o OS o SAN • Backup and Recovery
  27. 27. Summary 1. Focus first on your Applications and People 2. Derive RTOs and RPOs 3. Collect your data 4. Map requirements to infrastructure and technologies to best fit those individual needs
  28. 28. Questions? @joe_conlin