Redefinition of Business Continuity Strategies using Cloud Native Enterprise Architectures
1 like138 views
The document discusses the redefinition of business continuity and disaster recovery strategies through cloud-native enterprise architectures, particularly using SAP workloads on AWS. It highlights how these architectures improve scalability, reduce provisioning times, and ensure high availability while managing disaster recovery efficiently. The presentation also emphasizes the transition from traditional on-premise systems to cloud solutions and the resultant improvements in performance and cost-effectiveness.
Redefinition of Business Continuity Strategies using Cloud Native Enterprise Architectures
- 1. Frank Stienhans, CTO August 2016 Redefinition of Business Continuity Strategies using Cloud Native Enterprise Architectures
- 2. Both production and non-production landscapes are massively effected by the rewritten laws of physics in the cloud. One opportunity of Cloud Native Enterprise Architectures is to redefine the approaches to Business Continuity and Disaster Recovery. Using SAP workloads on AWS as example we will show how and why enterprises run different than before and how Disaster Recovery needs accelerate all in migrations to the cloud. Abstract
- 3. • Cloud Platform – using AWS as example • Cloud Transformation Impact • Cloud Best Practices • Cloud High Availability and Disaster Recovery • Making it Simple 24. janúar 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 3 Agenda
- 4. AWS Regions
- 5. Source: Gartner (August 2016) AWS Topology AWS Cloud AWS Region AWS Availability Zone AWS Data Center EC2 Hosts 1 1 1 EC2 Instances 1 1
- 6. AWS Topology AWS Cloud AWS Region AWS Availability Zone AWS Data Center EC2 Hosts 1 1 1 EC2 Instances 1 1 One Solution Architecture
- 7. Cloud Transformation Before and After Using the example of SAP HANA on Amazon Web Services
- 8. Provisioning Time: Infrastructure, Installation, Configuration SAP HANA Appliance 14 Weeks Ocean9 + AWS 15 minutes
- 9. Scale Out Time: Infrastructure, Installation, Configuration SAP HANA Appliance 14 Weeks Ocean9 + AWS 4 minutes
- 10. Hardware Refresh Time: Infrastructure, Installation, Migration SAP HANA Appliance 18 Weeks Ocean9 + AWS 60 minutes
- 11. Upfront Cost for Provisioning, Scale out, Hardware refresh SAP HANA Appliance $ XX,XXX Ocean9 + AWS $ 0
- 12. Be Prepared for Hardware Failure SAP HANA Standby Nodes $ XX,XXX Ocean9 + AWS EC2 Auto Recovery $ 0.50
- 13. How is this related to Business Continuity and Disaster Recovery ? 24. janúar 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 13
- 14. Cloud Sizing: Application Servers (SAP and beyond) On Premise Cloud Few Large Servers Many Smaller Servers
- 15. Enterprise Elasticity – A Year, A week, A day 0 1 2 3 4 5 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec AverageNetWeaverEC2Instances Reserved Instances On Demand Instances
- 16. Cloud Sizing: SAP Database On Premise Cloud One Large Server Large Server
- 18. HA Backup & Restore on AWS 1. Measure RPO in minutes 2. Durability of 99.999999999% 3. Recover any SAP HANA System in 2 hours or less from a backup 4. SAP HA on AWS can be cost neutral 5. Disaster Recovery HA Backup & Restore Strategy + AWS S3 Cross Region Backup Replication + AWS Route 53 Multi-VPC Assignment = DR Backup & Restore Strategy Closures of Datacenters
- 19. DEV / TEST Landscape 20 Amazon S3 Region CloudWatch AvailabilityZone SecurityGroup VPCSubnet SecurityGroup VPCSubnet Corporate Network AvailabilityZone PrimarySecondary Primary AD/DNS Router DB IAM Role IAM SAP Web Dispatcher SAP ABAP AS SAP JAVA AS SAP Central Services Amazon Route 53 Customer Router AWS CloudFormation
- 20. SAP HANA Multi-Site High Availability 1. Run SAP HANA in 2 or 3 Availability Zones to achieve an uptime of up to 99.99% 2. Do not fail back to something that failed once. 3. Analyze the error and terminate the faulty System Site. 4. Disaster Recovery HA Warm Standby Strategy + SAP HANA ASYNC System Replication + AWS S3 Cross Region Backup Replication + AWS Route 53 Multi-VPC Assignment = DR Warm Standby Strategy
- 21. Retail with SAP on AWS Availability Zone A Availability Zone B Availability Zone C S3Cloud Watch Route 53SNS S3 Route 53 Primary Region Secondary Region Auto Scaling Auto Scaling Auto Scaling Auto Scaling Auto Scaling Auto Scaling SAP System Sites
- 22. Sites / AZ Strategy % RPO / RTO Auto Recovery 1 Backup & Recovery 99.5 % 15 minutes / 2 hours 2 SAP HANA System Replication + Backup & Recovery 99.95 % ~ 0 / 1 minute 3 SAP HANA System Replication + Backup & Recovery 99.99 % ~ 0 / 1 minute 24. janúar 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 23 Ocean9 SLAs – SAP HANA on AWS
- 23. SAP HANA Database Recovery Time with Ocean9 and AWS 24. janúar 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 24
- 24. With one click • Strong identity and access management • Secure networking • Clustering across three availability zones for high availability and disaster recovery SAP Solution with 99.99% uptime
- 25. 24. janúar 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 26 Ocean9 LIVE
- 26. Thank you Contact us: questions @ ocean9.io More information: http://ocean9.io 24. janúar 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved27
- 28. Frank is an early cloud innovator with key architecture and operations contributions. In 2007, he was first to recognize the power of AWS for SAP use cases: His team build a self service SAP on AWS, serving more than 1000 employees with more than 11000 servers per month. Gaining tremendous operational expertise, SAP’s former CTO Vishal Sikka challenged Frank to demonstrate SAP HANA scalable performance with 1000 CPU cores, which were delivered as a SAP HANA aggregated system with 111 cloud machines. In 2013 Frank joined AWS Professional Services to build up the SAP Practice. He rolled out the first SAP HANA Production System in an Enterprise on AWS and many more since. Frank advised dozens of large global enterprises around the world on the best strategy, architecture and operations for SAP on AWS. At Ocean9, Frank’s team is continuously raising the bar for what is possible for Enterprise Solution Deployments and is passionate about assisting partners and customers in their journey to and in the cloud. Frank is considered the leading expert in his field and is the holder of 18 cloud related patents. 24. janúar 2017 © Copyright, 2016, Ocean9, Inc., All Rights Reserved 29 Presenter: Frank Stienhans, CTO