aws webcast - best practices for deploying sap workloads on aws
out of 49
Post on 15-Aug-2015
Embed Size (px)
- 1. 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Steven Jones, Sr. Manager, Solutions Architecture March 17th , 2015 Best Practices for Deploying SAP Workloads on AWS
- 2. SAP on AWS All SAP Business Suite and NetWeaver Applications (FI, HR, BI/BW, SRM, Solman, SAP PO, etc) Leverage Multi-AZ for Production Workloads x86 Intel Processor based systems with up to 32vCPUs x 244GIB RAM, SSD backed storage for 10s of thousands of IOPS S3 Storage provides 99.999999999 durability Enterprise level security Pricing, Sizing, Management and Operations SAP Supported Platform High Availability High Performance High Durability Secured platform Flexible 1 http://aws.amazon.com/whitepapers/vms-sap-tco/
- 3. SAP & AWS Relationship - Key Milestones 2008 20122010 2014 SAP as a Customer A1/B1 BOBJ HANA Developer Edition HANA One Afaria SAP HANA Platform Edition SAP Business Suite SAP Cloud Appliance Library (CAL) CustomerAdoption Time RDS Solutions Sybase IQ / ASE SAP HANA for B1
- 4. Backup / Recovery Deploy Operate DR/HA Scale Architecture AWS Leverage Faster Efficiently Agile Cost Efficient AWS Enables SAP Customers to Easily Reliable
- 5. Security
- 6. Architected for Enterprise Security Requirements Certifications and accreditations for workloads that matter The Amazon Virtual Private Cloud [Amazon VPC] was a unique option that offered an additional level of security and an ability to integrate with other aspects of our infrastructure.
- 7. AWS Shared Responsibility Model Facilities Physical security Compute infrastructure Storage infrastructure Network infrastructure Virtualization layer (EC2) Hardened service endpoints Rich IAM capabilities Network configuration Security groups OS firewalls Operating systems Applications Proper service configuration AuthN & acct management Authorization policies + = Customer . Scope of responsibility depends on the type of service offered by AWS: Infrastructure, Container, Abstracted Services Understanding who is responsible for what is critical to ensuring your AWS data and systems are secure! More secure and compliant systems than any one entity could achieve on its own at scale
- 8. Sizing and Performance
- 9. When sizing the HANA appliance, main memory is the most important resource. Sizing methods vary depending on the implementation scenario. In general the following methods apply: New Implementation: Use the SAP QuickSizer (http://service.sap.com/quicksizer) Migrating an Existing SAP Netweaver Business Warehouse System: Use the new ABAP sizing report for SAP NetWeaver BW described in SAP note 1736976* (http://service.sap.com/sap/support/notes/1736976) Migrating an Existing SAP Business Suite System to HANA: See SAP note 1872170* ( http://service.sap.com/sap/support/notes/1872170) to estimate the main memory requirements of the HANA virtual appliance. * SAP ID Required If memory requirements for the SAP HANA solution exceed the available memory of a single AWS instance, you can deploy a scale-out solution consisting of multiple instances as long as the SAP solution you are deploying supports a scale-out configuration.
- 10. Compute Optimized Name vCPU Memory (GiB) I/O Perf SAPS c4.8xlarge 36 60 10 Gigabit 37,950 c4.4xlarge 16 30 High 19,030 c4.2xlarge 8 15 High 9,515 c4.xlarge 4 7.5 High 4,758 c4.large 2 3.75 Moderate 2,379 c3.8xlarge 32 60 10 Gigabit 31,830 c3.4xlarge 16 30 High 15,915 c3.2xlarge 8 15 High 7,958 c3.xlarge 4 7.5 High 3,979 c3.large 2 3.75 Moderate 1,989 Memory Optimized Name vCPU Memory (GiB) I/O Perf SAPS r3.8xlarge 32 244 10 Gigabit 31,920 r3.4xlarge 16 122 High 15,960 r3.2xlarge 8 61 High 7,980 r3.xlarge 4 30.5 Moderate 3,990 r3.large 2 15 Moderate 1,995 Use in 2-Tier and 3-Tier Configurations Certified Instances for SAP HANA Cluster Networking Available EBS Optimized Instances Enhanced Networking
- 11. Follow standard Amazon EBS performance best practices outlined in the Amazon EC2 User Guide Amazon EBS General Purpose (SSD) volumes are recommended for most SAP system types Use EBS-optimized or 10 gigabit network instances for production systems General Purpose (SSD) Provisioned IOPS (SSD) Magnetic Recommend use cases Boot volumes Small to med DBs Most SAP Systems Extreme I/O intensive Large DBs Cold storage Storage media SSD-backed SSD-backed Magnetic-backed Volume size 1GB- 1TB 1GB- 1TB 1GB- 1TB Max IOPS per volume 3 IOPS/GB Burst up to 3000 IOPS 4,000 IOPS ~100 IOPS Read and write peak throughput 128 MB/s 128 MB/s ~50-90 MB/s Max I/O per node(16k) 48,000 48,000 48,000 Peak throughput node 800 MB/s 800 MB/s 800MB/s Latency (random read) 1-2ms 1-2 ms 20-40 ms API name gp2 io1 standard Price* $.10/GB-Month $.125/GB-Month $.065/provisioned IOPS $.05/GB-Month $.05/ 1M I/O
- 12. General Purpose (SSD) Provisioned IOPS (SSD) Magnetic Recommend use cases Boot volumes Small to med DBs Most SAP Systems Extreme I/O intensive Large DBs Cold storage Storage media SSD-backed SSD-backed Magnetic-backed Volume size Up to 16TB Up to 16TB 1GB- 1TB Max IOPS per volume 10,000 IOPS 20,000 IOPS ~100 IOPS Read and write peak throughput per volume 160 MB/s 320 MB/s ~50-90 MB/s Max I/O per node(16k) 48,000 48,000 48,000 Peak throughput node 800 MB/s 800 MB/s 800MB/s Latency (random read) 1-2ms 1-2 ms 20-40 ms API name gp2 io1 standard Price* $.10/GB-Month $.125/GB-Month $.065/provisioned IOPS $.05/GB-Month $.05/ 1M I/O Amazon EBS larger and faster volume types Amazon EBS Deep Dive: https://www.youtube.com/watch?v=xtuRD2AZt3M
- 13. SAP Sizing made easy Traditional Planning Horizon Planning Horizon on AWS ComputeRequirements
- 14. Physical Host XPhysical Host X AWS HypervisorAWS Hypervisor Virtual Machine Physical Host Physical Hardware Y Physical Hardware Y AWS HypervisorAWS Hypervisor SAP ECC Virtual Machine SAP ECC Virtual Machine Running Shutdown SAP Virtual Machine is unavailable Issue API Call to start Virtual Machine SAP Virtual Machine started on a new physical host EBS persistent Volumes are mapped by default SAP ECCSAP ECC Physical Host YPhysical Host Y AWS HypervisorAWS Hypervisor SAP ECCSAP ECC Running (new host) What about Hardware Refreshes? Change Instance type using AWS Console or API Call Physical Hardware X Physical Hardware X AWS HypervisorAWS Hypervisor SAP ECCSAP ECC Hardware upgrades in minutes! No data migration required Retain same IP addressing (VPC)
- 15. High Availability & Disaster Recovery
- 16. 11 Regions N. Virginia N. California Oregon GovCloud US Ireland Frankfurt Singapore Tokyo Sydney Sao Paulo China* 11 Regions N. Virginia N. California Oregon GovCloud US Ireland Frankfurt Singapore Tokyo Sydney Sao Paulo China* http://aws.amazon.com/about-aws/globalinfrastructure AWS Global Infrastructure 28 Availability Zones 51 Edge Locations 28 Availability Zones 51 Edge Locations * Limited public release
- 17. Distinct locations engineered to be insulated from failures in other Availability Zones Connected via an inexpensive, low latency network An independent collection of AWS services in a defined geographical location Foundation for meeting location dependent privacy and compliance requirements Customer has full control. AWS does not move customers resources Contains two or more Availability Zones AWS Regions and Availability Zones Region Availability Zone Availability Zone A Availability Zone B Availability Zone C Sample US Region
- 18. Physical Host XPhysical Host X AWS HypervisorAWS Hypervisor Virtual Machine Physical Host Physical Hardware Y Physical Hardware Y AWS HypervisorAWS Hypervisor SAP Virtual Machine SAP Virtual Machine Running Host/Hypervisor Failure or loss of network connectivity SAP Virtual Machine is unavailable Auto recovery for EC2 SAP Virtual Machine started on a new physical host EBS persistent volumes are mapped by default SAPSAP Physical Host YPhysical Host Y AWS HypervisorAWS Hypervisor SAP Virtual Machine SAP Virtual Machine Running (new host) Leverage AWS spare capacity for SAP High Availability Physical Hardware X Physical Hardware X AWS HypervisorAWS Hypervisor SAPSAP Result: Better uptime numbers, no waiting for hardware repairs Leverage hardware spares at no cost Cloud Watch Alarm Detect & Trigger
- 19. Multiple Data Center High Availability Availability Zone A Availability Zone B Availability Zone C Sample US Region
- 20. Multi-Region Deployments for Disaster Recovery SAP environments can also be deployed in a multi-region deployment model as AWS Regions are dispersed and located in separate geographic areas.
- 21. Backup and Recovery of SAP Systems on AWS The SAP on AWS Backup and Recovery Guide provides an overview of how to backup SAP systems running on AWS. The guide focuses on the essential differences in backing up SAP systems on AWS as compared to traditional infrastructure Backup Options: Create Amazon Machine Image (AMI) EBS Snapshots Backup to EBS Push backup to S3 with AWS Command Line Tools RMAN direct to S3 with encryption via Oracle Secure backup (OSB)
- 22. Deploying SAP Systems
- 23. Deploying new SAP systems from scratch The process to install an SAP solution on an Amazon EC2 instance is very similar to the process for any other physical or virtual server.
- 24. Download SAP Software directly from service marketplace to installation or bastion host. Use EBS volume to maintain a repo of installation software Leverage installation and operations guides @ http://aws.sap.com/sap SAPInst & Download Manager require X Windows environment on Linux. (i.e. NoMachine) Use Windows Server or Amazon Workspaces instance as jump station Deploying new SAP systems from scratch - Tips
- 25. Deploying new SAP systems from prebuilt images Certain SAP solutions are available as pre-buil
View more >