Architecting SAP solutions on Azure. Sujesh Kodoth Architect Norman Sequeira Cloud Solution Architect

Transcription

1 Learn. Connect. Explore.

2 Architecting SAP solutions on Azure Sujesh Kodoth Architect Norman Sequeira Cloud Solution Architect

3 Agenda SAP and Microsoft Scenarios Deployment Sizing Considerations

4 Microsoft and SAP partnership: Accelerating the momentum

5 SAP Certifications, Supported Products and Azure VM types Available Today & Near Term - Roadmap Available Now Near Term - Roadmap SAP Product Guest OS RDBMS VM Type All SAP Software based on SAP Application Server 7.x Windows SQL Server, ASE, Oracle A5, A6, A7, A8, A9 3 (This means More SAPS) All SAP All-in-One Windows SQL Server, ASE, Oracle A5, A6, A7, A8, A9 3 SAP Application Server 7.x (ABAP or/and Java) 1 Windows SQL Server, ASE, Oracle A5, A6, A7, A8, A9 3 SAP HANA Developer Edition (which includes HANA client software comprised of SQLDBC, ODBO (Windows only), ODBC, and JDBC drivers, HANA Studio, and HANA database) 2 Novell SUSE Linux N/A A7, A8 Tier VM Type VM Size SAPS 2-tier A5 2 CPU, 14 GB 1,500 3-tier A5 X 10 2 CPU, 14 GB 12,000 2-tier A6 4 CPU, 28 GB? 2-tier A7 8 CPU, 56 GB? 2-tier A9 16 CPU, 118 GB? 3-tier A? X?? Supported OS & RDBMS Platforms Windows Server 2008 R2, 2012 and 2012 R2 Microsoft SQL Server 2008 R2, 2012 or higher 4 ASE, Oracle to follow SAP License Customer can bring their own SAP application licenses SQL Server Database License Customer with Software Assurance can bring their own SQL Server licenses to Azure as license mobility benefits Newly purchase SQL Server Enterprise/Developer Edition Stay tuned for license mobility guidance for SQL 1 Only 7.00 and later SAP releases of are supported for deployment in Azure. (Details in note # ) Server runtime licenses purchased from SAP 2 HANA can not be used in conjunction with based applications (for the near term) and is to be deployed through SAP Cloud Appliance Library (CAL) 3 Even larger VM types if Azure will offer 4 SQL 2014 support is planned for Q (Subject to successful integration testing).

6 Support for HANA Products HANA Developer Edition can t be used for productive applications Can t be used in conjunction with based applications Can be deployed through SAP Cloud Appliance Library (CAL) to Microsoft Azure Supported VM Type: A7 & A8 (A8 = 8 cores, 56 GB RAM) Step-by-step guide of HANA on Azure HANA Developer Edition HANA One & HANA Enterprise Edition is in Roadmap Create a HANA instance from SAP Cloud Appliance Library HANA instance deployed on Microsoft Azure Connecting to HANA Database with HANA Studio

7 3-tier 2-tier SAP Architecture SAP is a client server model, uses tiered architecture. The three layers are as below; Presentation Presentation Layer Presentation Layer provides means of: Input, allowing the users to manipulate the system Output, allowing the system to produce the results of user s manipulation SAP is having Graphical User interface (SAP GUI). The SAP GUI is installed on Individual machines which act as presentation layer. Application Layer In this layer business logic is executed. The application layer can be installed on one machine, or it can be distributed among more than one system. The APPLICATION SERVER communicate with the presentation components, the database, and also with each other, using a Central Instance Database Layer The database layer holds the data. Application + SCS/A(SCS) Database Presentation Application + SCS/A(SCS) Database

8 1 Why SAP Non-Production Systems on Microsoft Azure?

9 1 SAP Non-Production Systems on Microsoft Azure Non-Production = Development, Test, Dry Run, Sand-box, Training (and Quality Assurance in a sense) Might not need full basis/platform support from SAP for Non-Production Applications in scope : SAP, ABAP/Java, HANA Developer Edition, SAP Objects and SAP/Sybase Mobile Platform Database / OS : SQL Server, Oracle, SAP/Sybase ASE etc / Windows or Linux SAP GUI, Transport, RFC and other protocols work transparently between on-premises and Azure (*) Database High Availability : SQL Server AlwaysOn, Mirroring, Log ship etc SAP GUI & Portal (DB) (DB) (DB) (DB) (AP/ (A)SCS) (AP/ (A)SCS) (AP/ (A)SCS) Transport (AP/ (A)SCS) Transport Site-to-Site VPN OR (DB) (DB) (AP/ (A)SCS) HANA (AP/ (A)SCS) Objects SAP Mobile Platform (DB) Dev (DB) (AP/ (A)SCS) (AP/ (A)SCS) Quality Assurance HANA Objects SAP Mobile Platform Domain Controller Domain Domain Controller Controller Production ExpressRoute HANA Objects SAP Mobile Platform Test (*) Domain Controllers are optional however needed for SQL Server AlwaysOn

10 2 Why SAP Production Systems on Microsoft Azure?

11 2 SAP Production Systems on Microsoft Azure SAP Applications in scope : SAP 6.x, 7.x (ABAP/Java) SAP Note , , Other SAP applications to follow Database / OS : SQL Server 2008 R2 64-bit or later / Windows Server 2008 R2 64-bit or later Other major databases/oss to follow Use database high availability functionality or/and ExpressRoute for stable network bandwidth when needed More specifically : Non-critical & non I/O intensive SAP / applications IOPS <= 8,000 IOPS (A7-A9) <= 4,000 IOPS (A6) <= 2,000 IOPS (A5) SAP GUI & Portal (*) Database High Availability : SQL Server AlwaysOn, Mirroring, Log ship etc Domain Legacy Controller SAP Applicati ons RFC File share etc Site-to-Site VPN OR (DB) (DB) (AP/ (A)SCS) HANA (AP/ (A)SCS) Objects SAP Mobile Platform (DB) Dev (DB) (AP/ (A)SCS) (AP/ (A)SCS) Production Domain Domain Controller Controller Domain Legacy Controller Applicati ons Production ExpressRoute HANA Objects SAP Mobile Platform Test (*) Domain Controllers are optional however needed for SQL Server AlwaysOn

12 3 Why SAP Disaster Recovery Systems on Microsoft Azure?

13 3 SAP Disaster Recovery Systems on Microsoft Azure Use DB disaster recovery solutions to have asynchronous SAP DB replica(s) on Azure During normal operations, AP servers can be switched off and DB servers can be very minimal Failover process is manual and recommended to test in advance Stop everything on-premises -> Change access path (DNS servers, SAP GUI) to the new AP servers -> Open the replica databases on Azure -> Start the SAP VMs on Azure Critical to note Disaster Recovery becomes Production in case of failover (*) Database High Availability : SQL Server AlwaysOn, Mirroring, Log ship etc (DB) (DB) (DB) (DB) (AP/ (A)SCS) (AP/ (A)SCS) (AP/ (A)SCS) (AP/ (A)SCS) Site-to-Site VPN OR (DB) (DB) (AP/ (A)SCS) HANA (AP/ (A)SCS) Objects SAP Mobile Platform (DB) Dev (DB) (AP/ (A)SCS) (AP/ (A)SCS) Disaster Recovery HANA Objects SAP Mobile Platform Domain Domain Controller Controller Domain Domain Controller Controller Production ExpressRoute HANA Objects SAP Mobile Platform Test (*) Domain Controllers are optional however needed for SQL Server AlwaysOn

14 SAP on Azure : Deployment Considerations System Types Support Scenarios Small Production Systems Development Systems Testing Systems Prototype Systems Learning / Demo Systems Supported VM Types Supported SAP Products / Releases Supported OS / DBMS releases for specific SAP releases Support for 2-tier, 3-tier configurations Support prerequisites Azure Only Hybrid-IT Resource Capabilities CPU / Memory work/io bandwidth # VHD Mounts

15 SAP on Azure : Deployment Scenarios Azure Only Virtual Machine deployments into Azure without dependencies into On-Premise customer network VMs themselves are accessible over public network Hybrid Deployment Deployment of single, multiple SAP VMs or complete SAP landscape into Azure with the requirement of being fully integrated into on-premise network Communications through VPN tunnel or ExpressRoute On-Premise AD/DNS extended into Azure Communication between SAP systems in Azure and on-premise transparent o o o o RFC STMS Printing Access to file shares

16 Azure-Only Scenario Virtual Machines deployed only in Microsoft Azure No network connectivity back to customer network. No extension of on premise AD / DNS servers Customers connect to the Virtual Machines through network endpoints opened to the Internet, most commonly Remote Desktop and PowerShell, protected by SSL. Typically Training, Demo, Learning, Sandbox or Gold systems.

17 Architecture SAP Deployment : Azure Only Note: HA shown in Diagram is just for representation; HA may not be a mandate requirement for Test, Dev & QA Requirement. Note: All SAP VMs on Azure will be running Monitoring Extension (Details on further Slide)

18 Architecture SAP Deployment : Azure Only Remote Access to SAP systems Configure Endpoints Configure SAP System Change parameters rdisp/keepalive_timeout and rdisp/keepalive Changing Firewall Settings within VM Configuring the SAP GUI

19 Architecture SAP Deployment : Azure Only (contd.) Virtual Machine deployments into Azure without dependencies into on-premise customer network (Small Production, Training or Demo environment) Considerations: VMs are accessible over public network. Direct network connectivity for the applications running within the VMs to the on-premises network of the customer is not necessary. Terminal Services/RDS is used to access the VM to either fulfill the trainings tasks or the demos. SAPGUI and Internet Explorer are installed and run directly on the VM. If multiple VMs form the trainings or demo scenario, network communication and name resolution needs to work between the VMs by clear defining Cloud Services and Virtual work for each environment. Communications between the VMs need to be isolated, so, that several of sets of VMs can be deployed side by side without interferences. The SAP system(s) (and VM(s)) represent a standalone scenario in Azure which only requires public internet connectivity for end user access and does not require a connection to other VMs in Azure. In case of demo and trainings scenarios which are realized in multiple VMs, an Active Directory and/or DNS service is required for each set of VMs.

20 Hybrid Scenario SAP Virtual Machines on Azure with persistent connectivity back to the customer network. Customers connect to the Virtual Machines through Site-to-Site VPN or ExpressRoute, accessing Azure as a persistent part of their network (RFC, Printing, SAP GUI, HTTP). Note: HA shown in Diagram is just for representation; HA may not be a mandate requirement for Test, Dev & QA Requirement. Note: Small Production environment can also be hosted on azure with on premise connectivity to attain SAP functional capabilities

21 Architecture SAP Deployment : Hybrid-IT Scenario (contd.) Deployment of single or multiple SAP VMs into Azure with connectivity to on-premise network Communications through Site-to-Site Virtual work or ExpressRoute On-Premise AD/DNS extended into Azure Communication between SAP systems in Azure and On-premise transparent to end-user SAP Transport Correction System (STMS), RFC Communication, Printing, Security (like SSO) work seamlessly Access to file shares Not Supported Running different layers of SAP applications in different deployment methods. e.g. running the DBMS layer on-premise, but the SAP application layer in VMs deployed as Azure VMs. Some components of a SAP layer in Azure and some on-premise. e.g. splitting Instances of the SAP application layer between on-premise and Azure VMs. Distribution of VMs running SAP instances of one system over multiple Azure regions is not supported. Distribution of VHDs mounted to a SAP VM over different storage accounts.

22 Demo

23 Deployment Options Azure Image Gallery Azure Private Image Gallery Existing SAP system Migration to Azure Use Windows/SQL Server Image in Azure Gallery i. Up to date Windows and SQL Server images available ii. Careful using Windows/SQL Server image will cost more and should not be used when bringing own SQL Server licenses iii. Usually customers are using Windows image only iv. Upload VHDs with data to Azure and map Azure disks to deployed VMs v. Install SAP software plus additional required software in those deployed VMs i. A lot of post-deployment work and configurations ii. Patch state of Windows OS changes over time in gallery images Build a Private Image with all necessary software components on premises i. Build one or several VMs with the necessary patch state of Windows, auxiliary software, eventually SAP and DBMS software ii. Generalize VM image on premises iii. Upload VHD with image into Azure iv. Add as private Azure Image to private Azure Image Gallery v. Deploy systems many times from that private image vi. Rename pre-installed SAP instances with Rename functionality of SWPM i. Less post-deployment work ii. Deployment to same storage account where the image resides. Configure SAP VM and VHDs on premises in way that it fits into Azure IaaS and upload VHDs i. Make sure that requirements of VHDs for Azure are fulfilled, like OS drive to be 127GB, Fixed Format VHDs etc. ii. Upload VHDs representing VM and data VHDs iii. Declare VHDs as Azure Disks iv. Deploy from Azure VM Disk once only v. Keep VM name and SAP system name the same vi. Download to on premise works seamless, Downloaded VHDs to on premise can be run on Hyper-V servers. i. Easiest way to move system to Azure ii. Move from Azure to on premises works the same way

24 Deployment Option : Existing SAP system Migration There are multiple ways to move SAP systems to Azure Upload VHD (Disk) to Azure which has SAP Software already installed in it Move Existing On-Premise Test & Dev to Azure a) P2V physical machine and then move b) System Copy (Homogeneous / Heterogeneous) Export / Import DB Detach and Attach Other Options a) LVM b) Transport (Object Move) Note: System Rename would be used if Hostname requires to be changed

25 Deployment Option : for HANA Instances Available from SAP Cloud Appliance Library (CAL) HANE Developer Rev. 80 Can be provisioned in 5 different regions currently.

26 Demo

27 SAP Sandbox on Azure : How it works?

28 High Level Architecture SAP Disaster Recovery Scenario Application server can be either installed and kept or can be created up in DR when required, No data or Config required to be replicated. Central Instance s Directory structure (\usr\sap) need to be available at DR Site; Windows Backup to Azure or Any Sync Tool or script can be used Selecting VPN or Express Route would completely depend on daily incremental growth of database Note: Dependent application/server (AD, etc.) would also need to be planned for Disaster recovery Note: RTO will also depend on replication mechanism one opts for and for RPO would majorly depend on work Connectivity (VPN vs Internet vs Express Route) For SQL, Following can be used; AlwaysOn, Log Shipping, Backup to Azure, Replication, etc.

29 High Level Architecture SAP Disaster Recovery Scenario Different Ways Using Application & Database replication ASR With InMage App based solution Manual restore from SQL & Windows backup/restore (restore from azure blob storage) Note: Dependent application/server (AD, etc.) would also need to be planned for Disaster recovery Note: RTO will also depend on replication mechanism one opts for and for RPO would majorly depend on work Connectivity (VPN vs Internet vs Express Route)

30 High Level Architecture SAP Disaster Recovery Scenario Planned Failover/Failback Shutdown App Tier Failover Availability Group using SQL Always-On PowerShell Scripts AG listener redirects to new primary Failover of App Tier Update App DNS via Script Test Failover Note: Dependent application/server (AD, etc.) would also need to be planned for Disaster recovery Note: RTO will also depend on replication mechanism one opts for and for RPO would majorly depend on work Connectivity (VPN vs Internet vs Express Route) Test Failover App Tier in an isolated network with a bridge to SQL network Test App via a client within private network Use read-only SQL Secondary to perform Read Test

31 SAP on Azure : Logical Reference Architecture Primary DC Traffic Manager DR DC AS1 AS 3 Data Backups Subnet 1 Subnet 2 Subnet 3 SAP Application Server Instances Domain Controller Active SAP SCS / (A) SCS Server Always ON Synchronous Replication SQL Server 2012 Passive AS 2 VNET VENT Connectivity Asynchronous Replication Application Servers (STOPPED) SCS / (A) SCS Server (Stopped) Domain Controller Passive Always ON Synchronous Replication SQL Server 2012 Passive AS 4 Subnet 4 Subnet 5 Subnet 3 Data Backups Gateway On-Premise DC Domain Controller AS ADFS Servers (DB / App / Oracle) Availability Set Cloud Service

32 Backup & Restore Options SQL Server backups to Azure Blob Storage Windows Server Backup By using this feature you can easily backup your application DB to Windows Azure Backups Virtual Machine by Using PowerShell or API Back up and restore of virtual hard disks using PowerShell Azure Backup / Restore (ASR) Create Backup Vault in Azure Install and register Agent and Vault credentials on VM Configure Backup policy (periodicity, retention period etc.) ASR coordinates replication and recovery of VMs across sites Systems Center VMM 2012 R2 has built in ASR support for direct communication with Azure VMs for replication and health monitoring. Orchestrated recovery to restore services Windows Azure Backup is suitable for any workload, file servers, SharePoint, SQL or others running as a VM on Windows Azure IaaS. You can backup on Local Drive or Online Storage (Azure) backup-full-integration-with-windows-azure-backup-whywin2012r2.aspx Snapshot Azure VM (point in time) Snapshots provide a way to back up a blob as it appears at a moment in time. Once a snapshot has been created, it can be read, copied, or deleted, but not modified Other Information DPM on Azure IaaS DPM is supported on any Azure IaaS virtual machine that is size A2 or higher. Installing the DPM agent, setting up the protection group, recovering data, and monitoring backup and recovery jobs 3 rd Party EVault Citrix Share File Cerebrata CloudXplorer

33 SAP on Azure : Sizing Considerations

34 Environment SAP landscape on premises environment 1 SAP ECC 1 EP 1 SM 1 SRM 1 - BW 60 Active users SQL DB size ~250GB Small SAP system # Steps DB size Data Growth %

35 Environment Sr. No SAP Software Items (Azure) Quantity Comments 1 ECC Application Server A5 Instance (2 Core, 14 GB RAM) 2 SQL Database Server - For ECC A5 Instance (2 Core, 14 GB RAM) 3 BI/BW Application Server A5 Instance (2 Core, 14 GB RAM) 4 SQL Database Server - For BI/BW A5 Instance (2 Core, 14 GB RAM) 5 EP Application Server A5 Instance (2 Core, 14 GB RAM) 6 SQL Database Server - For EP A5 Instance (2 Core, 14 GB RAM) 7 Solution Manager Application Server A5 Instance (2 Core, 14 GB RAM) 8 SQL Database Server - For SM A5 Instance (2 Core, 14 GB RAM) 9 SRM Application Server A5 Instance (2 Core, 14 GB RAM) 10 SQL Database Server - For SRM A5 Instance (2 Core, 14 GB RAM) 1 1 Disk X 200 GB 1 3 Disk X 100 GB 1 1 Disk X 200 GB 1 3 Disk X 100 GB 1 1 Disk X 200 GB 1 3 Disk X 100 GB 1 1 Disk X 200 GB 1 3 Disk X 100 GB 1 1 Disk X 200 GB 1 3 Disk X 100 GB 11 8TB Azure Blob Storage 8TB 3.8 TB of Data Disk, 4.2 TB for backup & Other use (per environment) 12 Bandwidth (Egress) 1TB 1TB of Egress Bandwidth Transfer per Month (0.5GB data egress / user / day) 13 Virtual work 744 Hours 1 Virtual work per environment Decision parameters : As per QuickSizer results, server for each workload is suggested at 2000 SAPS and 1300 IOPS. SAP 3-tier environment is proposed for each workload to further divide it between Application and Database server. Microsoft Azure A5 instance is suggested for all application servers which can provide 2 core, 14 Gb memory, and 1500 SAPS. 2 servers at each workloads will cumulatively yield 3000 SAPS. For each database server 3 data disks are proposed. Each data disk provides 500 IOPS, which cumulatively can yield maximum of 1500 IOPS.

36 Partner & 3rd Party Solutions SAP Backup, HA and DR Solution by In Mage (Microsoft Acquired) App Private Storage for Microsoft Azure High Availability Solution by Double Take 3 rd Party (SIOS) Solution for High Availability of Azure VM Transport Management Solution (RealTech) Sync changes from Prod to DR, Prod to Test/ Dev/ Learning, etc.

37 Partner & 3rd Party Solutions Manage SAP Environment with PowerShell By ConnMove Disaster-Recovery-/High Availability Solutions by Libelle Operation Manager - HANA Management Pack by OZSoft Operation Manager - SAP Process Monitoring By ConnMove

38 Sample text template

39 Column layout

40 Picture layout

41 Recommended/related sessions 1 Session Name Track, Hall, Time 2 Session Name Track, Hall, Time 3 Session Name Track, Hall, Time

42 References Related references for you to expand your knowledge on the subject <Quote related references here> technet.microsoft.com/en-in aka.ms/mva msdn.microsoft.com/

43 < QR Code will be given a week before Tech Ed > Tell us what you think Scan the QR code to evaluate this session.

44 Follow us online Twitter: <speaker s handle> Facebook facebook.com/microsoftdeveloper.india <optional> Twitter twitter.com/msdevindia