Learn. Connect. Explore. - Microsoft
Learn. Connect. Explore.
Architecting SAP solutions onAzureSujesh KodothArchitectNorman SequeiraCloud Solution Architect
Agenda SAP and MicrosoftScenariosDeploymentSizing Considerations
Microsoft and SAP partnership: Acceleratingthe momentum
Available NowSAP Certifications, Supported Products and Azure VM typesNear Term - RoadmapAvailable Today & Near Term - RoadmapSAP ProductGuest OSRDBMSVM TypeAll SAP Business Suite Software based on SAP NetWeaver Application Server 7.xWindowsSQL Server, ASE, OracleA5, A6, A7, A8, A93All SAP Business All-in-OneWindowsSQL Server, ASE, OracleA5, A6, A7, A8, A93WindowsSQL Server, ASE, OracleA5, A6, A7, A8, A93Novell SUSE LinuxN/AA7, A8SAP NetWeaver Application Server 7.x (ABAP or/and Java)1SAP HANA Developer Edition (which includes HANA client software comprised ofSQLDBC, ODBO (Windows only), ODBC, and JDBC drivers, HANA Studio, andHANA database) 2TierVM TypeVM SizeSAPSSupported OS & RDBMS Platforms2-tierA52 CPU, 14 GB1,500Windows Server 2008 R2, 2012 and 2012 R23-tierA5 X 102 CPU, 14 GB12,0002-tierA64 CPU, 28 GB?Microsoft SQL Server 2008 R2, 2012 orhigher 42-tierA78 CPU, 56 GB?ASE, Oracle to follow2-tierA916 CPU, 118 GB?3-tierA? X ?SAP LicenseCustomer can bring their own SAP applicationlicensesSQL Server Database LicenseCustomer with Software Assurance can bring theirown SQL Server licenses to Azure as license mobilitybenefitsNewly purchase SQL Server Enterprise/DeveloperEditionStay tuned for license mobility guidance for SQLServer runtime licenses purchased from SAPOnly NetWeaver 7.00 and later SAP releases of NetWeaver are supported for deployment in Azure. (Details in note #1928533)HANA can not be used in conjunction with NetWeaver 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 offer4 SQL 2014 support is planned for Q3 2014 (Subject to successful integration testing).12(This means More SAPS)
Support for HANA Products HANA Developer Edition can’t be used for productive applications Can’t be used in conjunction with NetWeaver 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 ition-on-microsoft-azure/ HANA Developer Edition http://scn.sap.com/docs/DOC-31722 http://scn.sap.com/docs/DOC-28294 HANA One & HANA Enterprise Edition is in RoadmapCreate a HANA instance fromSAP Cloud Appliance LibraryHANA instance deployedon Microsoft AzureConnecting to HANADatabase with HANA Studio
SAP ArchitectureSAP is a client server model, uses tiered architecture.The three layers are as below;Presentation Layer provides means of: Input, allowing the users to manipulatethe system Output, allowing the system to produce the results of user’smanipulation SAP is having Graphical User interface (SAP GUI). The SAP GUI isinstalled on Individual machines which act as presentation layer.2-tierPresentation LayerPresentationDatabaseApplication LayerDatabase LayerThe database layer holds the data.Presentation3-tierIn this layer business logic is executed. The application layer can be installedon 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 InstanceApplication SCS/A(SCS)Application SCS/A(SCS)Database
1Why SAP Non-Production Systems on Microsoft Azure ?
1SAP 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 Business Suite, NetWeaver ABAP/Java, HANA Developer Edition, SAP Business Objectsand 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 etcSAP GUI & CS)Quality inControllerProduction(*) Domain Controllers are optional however needed for SQL Server AlwaysOn
2Why SAP Production Systems on Microsoft Azure ?
2SAP Production Systems on Microsoft Azure SAP Applications in scope : SAP Business Suite 6.x, NetWeaver 7.x (ABAP/Java) SAP Note 1928533, 2015553, 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 Business Suite/NetWeaver applications IOPS 8,000 IOPS (A7-A9) 4,000 IOPS (A6) 2,000 IOPS (A5)(*) Database High Availability : SQL Server AlwaysOn, Mirroring, Log ship etcSAP GUI & PortalDomainLegacyConSAPtrollerApplicationsRFCFile share ainDomainConControllertrollerProduction(*) Domain Controllers are optional however needed for SQL Server AlwaysOn
3Why SAP Disaster Recovery Systems on Microsoft Azure ?
3SAP 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 r(AP/(A)SCS)NetWeaver(AP/(A)SCS)Disaster nDomainConControllertrollerProduction(*) Domain Controllers are optional however needed for SQL Server AlwaysOn
SAP on Azure : Deployment ConsiderationsSystem Types Small Production Systems Development Systems Testing Systems Prototype Systems Learning / Demo SystemsSupportScenarios Supported VM Types Azure Only Supported SAP Products /Releases Hybrid-IT Supported OS / DBMS releasesfor specific SAP releases Support for 2-tier, 3-tierconfigurations Support prerequisitesResource Capabilities CPU / Memory Network/IO bandwidth # VHD Mounts
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 therequirement 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 transparentooooRFCSTMSPrintingAccess to file shares
Azure-Only ScenarioVirtual Machines deployed only in MicrosoftAzureNo network connectivity back to customernetwork.No extension of on premise AD / DNS serversCustomers connect to the Virtual Machinesthrough network endpoints opened to theInternet, most commonly Remote Desktop andPowerShell, protected by SSL.Typically Training, Demo, Learning, Sandbox orGold systems.
Architecture SAP Deployment : AzureOnlyNote: 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)
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
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 notnecessary. 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 VMsby clear defining Cloud Services and Virtual Network for each environment. Communications between the VMs need to be isolated, so, that several of sets of VMs can be deployed side by side withoutinterferences. The SAP system(s) (and VM(s)) represent a standalone scenario in Azure which only requires public internet connectivity for end useraccess 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 foreach set of VMs.
Hybrid ScenarioSAP Virtual Machines onAzure with persistentconnectivity back to thecustomer network.Customers connect to theVirtual Machines throughSite-to-Site VPN orExpressRoute, accessingAzure as apersistent part of theirnetwork (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
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 Network 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.
Demo
Deployment OptionsAzure Image GalleryAzure Private Image GalleryExisting SAP system Migration toAzureUse Windows/SQL Server Image in Azure GalleryBuild a Private Image with all necessary softwareConfigure SAP VM and VHDs on premises in way that it fitscomponents on premisesinto Azure IaaS and upload VHDsi.Up to date Windows and SQL Serverimages availableii.iii.i.Make sure that requirements of VHDs for Azurepatch state of Windows, auxiliary software,are fulfilled, like OS drive to be 127GB, Fixedimage will cost more and should not beeventually SAP and DBMS softwareFormat VHDs etc.used when bringing own SQL Serverii.Generalize VM image on premisesii.Upload VHDs representing VM and data VHDslicensesiii.Upload VHD with image into Azureiii.Declare VHDs as Azure DisksUsually customers are using Windowsiv.Add as private Azure Image to private Azureiv.Deploy from Azure VM Disk once onlyImage Galleryv.Keep VM name and SAP system name the sameDeploy systems many times from that privatevi.Download to on premise works seamless,Upload VHDs with data to Azure andv.map Azure disks to deployed VMsv.i.Careful using Windows/SQL Serverimage onlyiv.Build one or several VMs with the necessaryInstall SAP software plus additionalvi.required software in those deployedimageDownloaded VHDs to on premise can be run onRename pre-installed SAP instances withHyper-V servers.‘Rename’ functionality of SWPMVMsi.ii.A lot of post-deployment work andi.Less post-deployment worki.Easiest way to move system to Azureconfigurationsii.Deployment to same storage account whereii.Move from Azure to on premises works thePatch state of Windows OS changes overtime in gallery imagesthe image resides.same way
Deployment Option : Existing SAP system MigrationThere 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 Azurea) P2V physical machine and then moveb) System Copy (Homogeneous / Heterogeneous) Export / Import DB Detach and Attach Other Optionsa) LVMb) Transport (Object Move)Note: “System Rename” would be used if Hostname requires to be changed
Deployment Option : for HANA Instances Available from SAP Cloud Appliance Library (CAL) HANE Developer Rev. 80 Can be provisioned in 5 different regions currently.
Demo
SAP Sandbox on Azure : How it works ?
High Level Architecture SAP Disaster Recovery Scenario Application server can be eitherinstalled and kept or can becreated up in DR when required,No data or Config required tobe replicated. Central Instance’s Directorystructure (\usr\sap) need to beavailable at DR Site; WindowsBackup to Azure or Any SyncTool or script can be used Selecting VPN or Express Routewould completely depend ondaily incremental growth ofdatabaseNote: Dependent application/server (AD, etc.) would also need to be planned for Disaster recoveryNote: RTO will also depend on replication mechanism one opts for and for RPO would majorly depend onNetwork Connectivity (VPN vs Internet vs Express Route) For SQL, Following can be used;AlwaysOn, Log Shipping, Backupto Azure, Replication, etc.
High Level Architecture SAP Disaster Recovery ScenarioDifferent Ways Using Application & Databasereplication ASR With InMage NetApp based solution Manual restore from SQL &Windows backup/restore (restorefrom azure blob storage)Note: Dependent application/server (AD, etc.) would also need to be planned for Disaster recoveryNote: RTO will also depend on replication mechanism one opts for and for RPO would majorly depend onNetwork Connectivity (VPN vs Internet vs Express Route)
High Level Architecture SAP Disaster Recovery ScenarioPlanned Failover/Failback Shutdown App Tier Failover Availability Group using SQLAlways-On PowerShell Scripts AG listener redirects to new primary Failover of App Tier Update App DNS via ScriptTest Failover Test Failover App Tier in an isolatednetwork with a bridge to SQLnetwork Test App via a client within privatenetworkNote: Dependent application/server (AD, etc.) would also need to be planned for Disaster recoveryNote: RTO will also depend on replication mechanism one opts for and for RPO would majorly depend onNetwork Connectivity (VPN vs Internet vs Express Route) Use read-only SQL Secondary toperform Read Test
SAP on Azure : Logical Reference ArchitectureTraffic ManagerPrimary DCDR DCAS1AS 3Subnet 4Subnet 1SAP Application Server InstancesVNET – VENTConnectivityApplication Servers (STOPPED)On-Premise DCSubnet 5Subnet 2GatewaySCS / (A) SCS Server (Stopped)SAP SCS / (A) SCS ServerADFSDomainControllerSubnet 3Data BackupsAS 2AsynchronousReplicationDomainControllerSubnet 3DomainControllerAlways – ONAlways – ONActiveSynchronousReplicationSQL Server 2012PassiveSynchronousReplicationServers (DB /App / Oracle)AS 4Data BackupsPassivePassiveSQL Server 2012ASAvailability SetCloud Service
Backup & Restore OptionsSQL Server backups to Azure Blob StorageWindows Server Backup 2.aspxWindows Azure Backup is suitable for any workload, file servers, SharePoint , SQL or othersrunning as a VM on Windows Azure IaaS. You can backup on Local Drive or Online Storage(Azure) the-cloud.aspx n-with-windows-azure-backup-whywin2012r2.aspx / -windows-azure.aspxBy using this feature you can easily backup your application DB to Windows Azure .Backups Virtual Machine by Using PowerShell or APIBack up and restore of virtual hard disks using PowerShell.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. spx spx indows-azure-by-using-powershell.aspx -a-snapshot-b1dd8ba4 spx How-to-use-a-blob-snapshot-7aafa5c9Azure 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 withAzure VMs for replication and health monitoring. Orchestrated recovery to restore servicesOther 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, andmonitoring backup and recovery jobs 3rd Party EVault Citrix Share File Cerebrata CloudXplorer
SAP on Azure :Sizing Considerations
Environment SAP landscape onpremisesenvironment 1 – SAP ECC 1 – EP 1 – SM 1 – SRM 1 - BW 60 Active users SQL DB size 250GB Small SAP system –# StepsDB sizeData Growth %
EnvironmentSr. NoSAP SoftwareItems (Azure)QuantityComments1ECC Application ServerA5 Instance (2 Core, 14 GBRAM)11 Disk X 200 GB2SQL Database Server - For ECCA5 Instance (2 Core, 14 GBRAM)13 Disk X 100 GB3BI/BW Application ServerA5 Instance (2 Core, 14 GBRAM)11 Disk X 200 GBDecision parameters : As per QuickSizer results, serverfor each workload is suggestedat
Architecting SAP solutions on Azure Sujesh Kodoth Architect Norman Sequeira Cloud Solution Architect. . Microsoft SQL Server 2008 R2, 2012 or higher4 ASE, Oracle to follow . 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 .
Oct 18, 2017 · Silver: Cigna Connect 2500, Cigna US-TN Connect 3500, Cigna Connect 3000 Tri-Cities: Bronze: Cigna Connect 7000, Cigna Connect 5250 Silver: Cigna Connect 4750, Cigna Connect 4500 Bronze: Cigna US-TN Connect 6650, Cigna Connect HSA 5000, Cigna Connect 6400 Silver: Cign
o Microsoft Outlook 2000 o Microsoft Outlook 2002 o Microsoft Outlook 2003 o Microsoft Outlook 2007 o Microsoft Outlook 2010 o Microsoft Outlook 2013 o Microsoft Outlook 98 o Microsoft PowerPoint 2000 o Microsoft PowerPoint 2002 – Normal User o Microsoft PowerPoint 2002 – Power User o Microsoft PowerPoint 2002 – Whole Test
Business Ready Enhancement Plan for Microsoft Dynamics Customer FAQ Updated January 2011 The Business Ready Enhancement Plan for Microsoft Dynamics is a maintenance plan available to customers of Microsoft Dynamics AX, Microsoft C5, Microsoft Dynamics CRM, Microsoft Dynamics GP, Microsoft Dynamics NAV, Microsoft Dynamics SL, Microsoft Dynamics POS, and Microsoft Dynamics RMS, and
Microsoft, Microsoft Dynamics, logo systemu Microsoft Dynamics, Microsoft BizTalk Server, program Microsoft Excel, Microsoft.NET Framework, program Microsoft Outlook, Microsoft SharePoint Foundation 2010, Microsoft SharePoint Ser
Perform Endpoint Analysis Using AMP for Endpoints Console - Explore File Ransomware Protection by Explore Cisco Stealthwatch Enterprise v7.0 - Explore the Cisco Cloudlock Dashboard and User Security - Explore Cisco Cloudlock Application and Data Security - Explore Cisco Stealthwatch Cloud - Explore Stealthwatch Cloud Alert Settings,
K-2 Water Unit Table of Contents Lesson 1 : Water Introduction Explore: Water Detectives Lesson 2: Water and the Human Body . Lesson 5: Water and the Seasons Explore: Weather Calendar Explore: Precipitation Meter Explore: The Weight of Snow Lesson 6: Riparian Life Explore: The Riparian Web Explore: Riparian Field Day Glossary Resources .
Microsoft Dynamics 365 for Operations on-premises, Microsoft Dynamics NAV, Microsoft Dynamics GP, Microsoft Dynamics SL, Microsoft Dynamics AX 2012 or prior versions, or Microsoft Dynamics CRM 2016 or prior versions. This guide is not intended to influence the choice of Microsoft Dynamics products and services or provide technical specification.
References to Microsoft Word, Microsoft Excel, and Microsoft PowerPoint are to the latest version of Microsoft Office as of May 1, 2005. The information on Microsoft Word, Microsoft Excel, and Microsoft PowerPoint contained herein has been derived from the applicat
