Mejora tu estrategia de HA y DR

Size: px

Start display at page:

Download "Mejora tu estrategia de HA y DR"

Marvin Stevens
5 years ago
Views:

1 Mejora tu estrategia de HA y DR para SAP en Azure Dave Rendon Microsoft Azure MVP

2 Agenda Opciones de implementación Dimensionamiento y definición de arquitectura Herramientas de administración Estrategia de HA y DR Apoyo de migración

Evolution of SAP: 1980s SAP R/2 (mainframe) 1990s SAP R/3 (client-server) 2010 SAP HANA 2015 S/4HANA Traditional Architecture 3-tier Application Layer R/3 Architecture ECC CRM SCM BW SAP Netweaver

3 Evolution of SAP: 1980s SAP R/2 (mainframe) 1990s SAP R/3 (client-server) 2010 SAP HANA 2015 S/4HANA Traditional Architecture 3-tier Application Layer R/3 Architecture ECC CRM SCM BW SAP Netweaver Layer Certified Database SQL Server Orcl DB2 Sybase ASE HANA HANA Side-Car or HANA Standalone S/4HANA: New Architecture BW Netweaver SQL Server HANA EDW HANA Finance Order to Cash HANA Procure to Pay Request to Service SAP Cloud Platform HANA

4 SAP Cloud Platform early-2017 Business Network Applications IOT Extensions Digital Boardrooms Platform SAP Cloud Platform Cloud Roambi Suite Platform Analytics Any DB Hadoop

5 HANA What is SAP HANA? HANA is a brand that represents SAP s solution to any business problem. Deployment options include on-premises as a database appliance, or in the cloud through SAP or AWS. At the core of this real-time data platform is the SAP HANA database. HANA is a Database HANA is sold as an Appliance HANA is a platform for cloud In-memory database software Column and Row based stores for both analytical and transactional workloads Database engine supports SQL (JDBC/ODBC) and MDX (ODBO) Calculation Engine, Aggregation Engine, MDX Engine, Planning Engine and SQL Processor on persistency layer: Page management and logging Database plus pre-configured hardware Optimized appliance delivered by HW partners (HP, Dell, Cisco, IBM, etc.) All-in-one platform to power all SAP solutions Runs on Linux (SUSE) Cloud platform with HANA as the underlying technology HANA running on AWS (primarily test/dev, limited production scenarios) SAP and AWS relationship is tenuous HANA Cloud Platform (SAP cloud service) HANA on VMWare for test/dev Persistent Storage: Log entry SUSE Linux Enterprise is the recommended and supported OS of choice Remember SAP will discount other software to subsidize the initial cost of HANA. However, costs don t scale well with data growth because all data must be in-memory. So as data volumes grow, software and hardware become prohibitively expensive.

6 SAP HANA Platform: HEC, HPC, etc. SAP HANA is an in-memory data platform that is deployable as an on-premises appliance, or in the cloud. It is a platform that s best suited for performing real-time analytics, and developing and deploying real-time applications.

7 Why is so attractive on SAP workload on Azure? Customers usually run 3-15 different SAP products For every product the customer has at least 3 systems like: Production, Test and Development For some of the main systems, like SAP ERP customers have up to 10 systems Many servers or VMs motivate customers to look for less expensive infrastructure opportunities Projects often require systems with limited life time Projects often require short time to deploy systems no time for procurement of infrastructure

8 Scenarios customers use SAP Run parts of SAP landscape or whole SAP landscape on Azure Have Site-To-Site or Express Route connectivity between Azure and on-premise datacenter Deploy SAP systems in Azure VMs Customer are in various stages in this process From having a few small development or non-production system To having their whole SAP landscape in Azure Largest one with 7TB SAP ERP and 4TB SAP BW used by a few thousand users

9 Journey to Cloud: Roadmap for SAP ERP Customers On premise Multi-Vendor A Lift and Shift to Cloud SAP anydb As-a-Service Migration to HANA, Conversion to S/4HANA S/4HANA As-a-Service Analytics Non-SAP ERP, Industry Add-ons Any DB B C Brownfield, Cloud is the driver Reduce IT TCO, Test/Dev Market: 10% Lift and Migrate to Cloud Brownfield, Cloud is the driver Reduce IT TCO, Reduce Oracle/DB2 Licensing: Market 40% Lift and Shift/Migrate to Cloud, Migrate part to HANA Brownfield, Cloud + HANA is the driver Reduce IT TCO Market 45% Non-SAP, Custom Analytics ERP, Industry Add-ons Any DB Migrate to HANA SAP HANA As-a-Service Non-SAP, Custom Analytics ERP, Industry Add-ons HANA Conversion to S/4HANA or BW/4HANA Non-SAP, Custom Industry Solutions Embedded Analytics S/4HANA HANA D Transformation to S/4HANA and Cloud: Consolidation or (selective) Re-implementation or Greenfield Greenfield, Business is the driver Significant Business Value, Reduce IT TCO Market: Net New <5% Select Scope Variants: S/4HANA Finance S/4HANA Central Finance S/4HANA EM for SMB S/4HANA EM Public Cloud S/4HANA SCM

10 Your SAP HANA options on Azure PURPOSE-BUILT INFRASTRUCTURE Up to 0.5 TB RAM Globally available 1.7 TB to 3.5 TB RAM Launching soon in US, EU Largest scale (0.768 TB to 20 TB RAM) Available in US, EU, AUS

11 Extensive compute options for all workloads HIGHEST VALUE LARGEST SCALE-UP

12 AZURE VM SKUs SUPPORTED VM Type VM Size 2-Tier SAPS 3-Tier SAPS DB Server for 3-Tier Supported Required Azure Storage for Database Files A5 2 CPU, 14 GB 1,500 12,000 Yes Standard A6 4 CPU, 28 GB 3,000 25,000 Yes Standard A7 8 CPU, 56 GB 6,000 50,000 Yes Standard A8 / A10 8 CPU, 56 GB 11,000 *** No Standard A9 / A11 16 CPU, 112 GB 22,000 *** No Standard D11 2 CPU, 14 GB 2,325 *** Yes Standard D12 4 CPU, 28 GB 4,650 *** Yes Standard D13 8 CPU, 56 GB 9,300 *** No Standard D14 16 CPU, 112 GB 18,600 *** No Standard DS11* 2 CPU, 14 GB 2,325 *** Yes Premium DS12* 4 CPU, 28 GB 4,650 48,750 Yes Premium DS13* 8 CPU, 56 GB 9,300 91,050 Yes Premium DS14* 16 CPU, 112 GB 18,600 *** Yes Premium DS11v2 2 CPU, 14 GB 3530 *** Yes Premium DS12v2 4 CPU, 28 GB 6860 *** Yes Premium DS13v2 8 CPU, 56 GB *** Yes Premium DS14v2 16 CPU, 112 GB *** Yes Premium DS15v2 20 CPU, 140GB *** Yes Premium GS1** 2 CPU, 28 GB 3,580 34,415 Yes Premium GS2** 4 CPU, 56 GB 6,900 78,620 Yes Premium GS3** 8 CPU, 112 GB 11, ,520 Yes Premium GS4** 16 CPU, 224 GB 22, ,880 Yes Premium GS5** 32 CPU, 448 GB 41,670 *** Yes Premium *) The DS series in a 3-tier configuration is only supported with DB data files and DB transaction log files placed on Azure Premium Storage. **) The GS series (2-tier and 3-tier) is only supported with DB data files and DB transaction log files placed on Azure Premium Storage. ***) Please check with through SAP customer message on specifics of this configuration

SAP Deployment on Azure in Hybrid IT scenario Communications through VPN tunnel or ExpressRoute connection On-Premise AD/DNS extended into Azure On-premise and Azure located SAP systems in same

13 SAP Deployment on Azure in Hybrid IT scenario Communications through VPN tunnel or ExpressRoute connection On-Premise AD/DNS extended into Azure On-premise and Azure located SAP systems in same domain/ad Communication between SAP systems in Azure and on-premise completely transparent Every single customer using SAP on Azure beyond demo or trainings scenario is using this setup with VPN/ExpressRoute Supported for Hybrid and productive SAP landscapes in Azure

14 Selection criteria of Azure VMs for SAP Not all Azure VM types are certified for SAP Minimum requirements for VMs: At least 2 vcpus Ratio between memory and vcpu at least 6:1 Not all Azure VMs qualify Other rules for certification of VM SKUs: Some of the VM SKUs are exclusively certified with Premium Storage. E.g. No SAP certification for G-series, but certification of GS-Series If largest VM within a VM series does not show good enough results with Standard Storage, we will not certify any of the VMs of the series and rather wait for VM series being available with Premium Storage. E.g.: Dv2 series We are not making any difference between VMs for the SAP application layer (as good as no storage interaction) and DBMS VMs (sensitive to storage latency and throughput

15 Azure Storage Standard Storage Working in conjunction with all VM-Series Costs of disks based on stored data in disk and not by nominal size of disk E.g. Disk defined with 1TB size and filled with 100GB data charges will be for 100GB only Standard Azure disk has a limited IOPS quota of 500 IOPS Use Striping or Storage Pools to overcome IOPS limits per VHD IOPS quota multiply with number of disks engaged in Storage Pool E.g. build Storage Pool over 4 disks means roughly a limit of 4 x limit of single disk Not really suitable for DBMS storage traffic when SAP system has some workload Expect storage write latency like SQL Server Tlog writes being in the 15-40ms and read latencies also in the double digit space

16 Azure Storage - Premium Working with DS/GS VM series so far Provides fast read/write cache that is backed by local SSD drives on compute node. Up to 1TB disk cache size dependent on VM type Three different types of disks (see table) Moving disks from Standard Azure Storage to Premium Storage that don t hit the exact sizes of the three different categories are snapped to next larger category. E.g. a disk defined with 200GB would be categorized as P20 disk Charged by nominal size independent of data stored in disk even pay for empty disks Preferred for DBMS layer of SAP deployments

18 SAP HANA on Azure offering SKU approach Four offerings reflect different performance attributes: Compute, RAM, storage, and networking pre-configured Additional storage acquired separately if needed EA only SKUs transacted through EA amendment Customer benefits Better use of capital relative to on-premises deployments Overall solution spans hosted and cloud, providing better economics Flexible payment terms through Microsoft EA Configurations for SAP HANA on Azure (Large Instances) SAP Solution SKU (CPU) RAM Storage SAP Business Warehouse on/or SAP HANA Platform or Enterprise Edition (OLAP) 2 x Intel Xeon Processor E v3 768 GB 3 TB 4 x Intel Xeon Processor E v3 1.5 TB 6 TB SAP Business Suite on SAP HANA or S/4HANA (OLTP) 2 x Intel Xeon Processor E v3 1.5 TB 6 TB 4 x Intel Xeon Processor E v3 3 TB 12 TB

19 Azure as supported SAP Platform Services SAP NetWeaver Configurations supported: SAP NetWeaver 2-Tier and 3-Tier configurations are supported Production SAP landscapes only supported in cross-premises scenarios DBMS and complete SAP application layer need to be in one location (either on-premise or on Azure) see next slide All components of a SAP application layer need to be in the same location (either Azure or on-premise) If using VPN tunnels, necessary ports in VPN device need to be opened to make communication between SAP systems transparent Ports leveraged by SAP are documented here:

20 Supported/Not Supported Supported: Distinct Test/Production Systems in different premises NOT Supported: Application layer and DBMS layer in different locations Azure and onpremise Different Azure Regions

21 What to consider for SAP NetWeaver Before moving systems in Azure IaaS the following things need to be considered: Limitations of different Azure VM SKUs ( SAPS throughput as shown earlier (documented in SAP Note SAP Applications on Azure: Supported Products and Azure VM types Storage Throughput and latency. Compare Azure Standard Storage/Azure Premium Storage against requirements Network latency Compare VPN to ExpressRoute Sensitive data and compliance regulations Identify compliance concerns in regards to sensitive data being moved in public cloud Configuration changes Systems which run in 2-Tier configuration on-premise might require 3-Tier configuration in Azure

22 Business requirements Minimum data loss in case of a disaster 2. Failover complete within hours including SAP application layer 3. Clear failover process 4. Failover transparent to users and sub systems 5. Minimum costs for DR IT requirements 1. Production environment is on virtualization, bare metal or cloud 2. Minimum overhead on Production systems and network 3. Retire traditional SAN/Tape-based solutions

HA/DR considerations for SAP deployments on Azure SAP application layer has a Single point of failure with CI/ASCS/SCS where two processes are critical for whole system SAP uses Windows Server

23 HA/DR considerations for SAP deployments on Azure SAP application layer has a Single point of failure with CI/ASCS/SCS where two processes are critical for whole system SAP uses Windows Server Failover Cluster to secure their SPOF Azure does not support Shared Disks as necessary for configuring WSFC configurations suitable for SAP CI/ASCS/SCS Use 3 rd party SIOS Datakeeper to create Windows Server Failover Cluster with Shared Disk: Customers already productive with this solution

24 HA/DR considerations for SAP deployments on Azure DBMS use DBMS HA functionalities other than Windows Clustering in Azure SAP Central services use Clustering on top of SIOS Datakeeper SAP application instances just deploy them in same Azure Availability Set

25 Structure of SAP/DBMS VM in Azure IaaS Base VM VHD including OS and Executables plus all other VHDs have a limit of 1TB each Database files need to be located on separate data VHDs and mounted to deployed VM D:\ drive presented in VM is temporary drive of VM which is NOT persisted A5-A7 VMs: Drive should NOT be used for SAP and DBMS deployments, even not for tempdb or temp tablespace A8-A11, D/DS(v2) and GS-Series VMs: tempdb or temp tablespace can be placed on D:\ Drive. A8-A11, D/DS and GS-Series VMs: can be used for SQL Server 2014 Bufferpool Extension as well

26 Structure of SAP/DBMS VM in Azure IaaS VM booted from base VHD that is located on Azure Storage Use Windows Storage Spaces to build LUNs over multiple VHDs for data files (depends on IOPS demand) Eventually use Storage Spaces for Transaction Log as well

27 Recommendations for SAP deployments Deployment Method Do NOT deploy in ASM anymore Use Azure Resource Management as deployment framework Azure VNet: Make sure that Azure VNet gateway has enough throughput. Choose: High Performance SKU Ultra Performance SKU Keep in mind that single stream throughput through VNet gateway might be less than overall throughput In case of using ILB for building up Windows Clusters use DirectServerReturn option for shares (port 445)

28 Recommendations for SAP deployments VM SKU usage: Leave hands off A-series VMs and focus on D/DS(v2)-Series VMs For more high-end DBMS VMs use GS-series where available Be aware that GS-Series only in 7 Regions so far (with more to come) Prefer DSv2 wherever it is available Usage of Storage: For DBMS layer use Premium Storage where adequate performance is expected. Use Standard Storage for systems where expectations are low Standard Storage is hardly adequate for DBMS Not only SQL Server s Tlog file is critical Data files are critical as well since long latency in checkpoint writing can cause severe latch contention Standard Storage is fine for SAP Application Layer

29 Recommendations for SAP deployments Caching of VHDs Standard Storage: Data and Log VHDs: No Caching Caching of VHDs Premium Storage: Data files: Read Caching Log files: No Caching Don t use Read/Write caching Keep in mind that there are limits to storage bandwidth on single VM level with Premium Storage 10 x P30 already provide maximum bandwidth ( 3 x 200MB/sec) of highest VM throughput (GS5 = 2GB/sec)

30 Recommendations for SAP deployments Locating SQL Server database files directly as Blob onto Premium Storage: You have no Premium Storage Cache on the Compute node You are not getting the throughput SLAs as with having the database files in VHD on Premium Storage But you have a larger D:\ drive for SQL Server Buffer Pool Extension and tempdb: Using SQL Server backup directly against Azure Blob Storage: Works sufficiently well for small databases of double digit GB beyond that not so great Some significant improvements with SQL Server 2016 Azure Backup which allows backup of SQL Server databases as well these days, stretches the limits, but also has its usability limits when a DB is multiple TB

31 Recommendations for SAP deployments Backup: Customers got used to keep several database backup handy on SAN drives attached to servers allows fast built up of sandbox systems or refreshing systems Customers want to avoid interaction with centralized backup solution by this Hard to mimic this since our VHD sizes are limited to 1TB. Hence several of our customer went with Commvault Backup solutions: Customers asking for Encryption of data Use SQL Server TDE and Azure Key Vault as EKM solution Need to install an adapter to create this solution Adapter can be downloaded here:

32 Road To Virtualization & Azure In 2014: 520 Servers 61% Physical Hardware 39% On-Prem VMs Middle 2017: 1% Physical Hardware 64% On-Prem VMs 35% Azure 3% 1% 39% 61% 27% 50% 49% 70%

33 Av. Set 3, WSFC Av. Set 2 Av. Set Av. Set 1, WSFC SQL AG

34 Summary: SAP HANA on Azure Eliminate single point of failure: Hardware redundancy Network redundancy Datacenter redundancy HA support: Backups Storage replication Host Auto-failover

35 High Availability Decision Tree

36 Deploy SAP NetWeaver and SAP HANA on Azure

37 SAP Administrative Tools SAP HANA Cockpit Core administration and detailed monitoring of a single SAP HANA Database Web-based SAP Fiori launchpad Runs on SAP HANA XS Classic SAP DB Control Center Administration and monitoring of the entire SAP HANA Database landscape Web-based SAP Fiori launchpad Runs on SAP HANA XS Classic SAP HANA Studio SAP HANA basic administration tasks development included modeled views Eclipse-based IDE No longer in feature development

38 Customer Case Studies KordiaGroup with our partner Syd: non-production VMs, with Syd, Telecom : Zespri with Datacom (video): production VMs, partner Datacom, Consumer Goods: PACT Group, Australia El Tejar: Argentina, production VMs with O365, partner Wezen Group, Consumer Goods: Frunze: Ukraine, non-production VMs, Manufacturing: BekaertTextiles Group (video): Belgium, SAP DRP, partner Oxya, Consumer Goods: Al MuhaidibGroup: Saudi Arabia, SAP DR in Azure: Softtek: Mexico, non-production VMs, IT Services: Alvogen: Croatia, Pharma, SAP DR in Azure, partner S&T: Kompasspress article here (in French): France, win back AWS, SAP Hybris in production

Wharfedale Technologies Inc. Whitepaper January SAP HANA on Public Cloud (Azure)... 3

Wharfedale Technologies Inc. Whitepaper January SAP HANA on Public Cloud (Azure)... 3 Table of Contents SAP HANA on Public Cloud (Azure)... 3 Overview...3 Why Public Cloud for HANA...3 SAP HANA Products Certified for Use on Azure...4 Deployment Options...5 HANA on Azure VMs... 5 HANA on