Azure Infrastructure for SAP® - General Build Guidance

Prepared for

[Type Customer Name Here] 5/8/2023Version 1 Final

Prepared by

[AUTHOR][Type Author Position Here][Type Author Email Here]

Contributors DOCPROPERTY Contributors \* MERGEFORMAT [Type Contributors Here]

Azure Infrastructure for SAP® - General Build Guidance

ii

Revision and Signoff Sheet

Change RecordDate Author Version Change Reference

1 Initial draft for review/discussion

ReviewersName Version Approved Position Date

Table of Contents

1 Overview....................................................................................................12 SAP® on Azure Deployment Planning........................................................23 SAP® on Azure Installation Requirements.................................................34 Before Installation......................................................................................45 During Installation......................................................................................5

5.1 SAP® SQL Server Database...........................................................................55.2 SAP® Application Server and Central Services..............................................55.3 Sample SAP® ECC on Azure Installation........................................................5

1 OverviewSAP® Business suite comes with many applications like Enterprise Core Components (ECC), Customer Relationship Management (CRM), Governance Risk and Compliance (GRC), and many more. SAP® has master guide and installation guide for every application on all Operating Systems (OS) and relational data management system (RDBMS). In all <Partner> Services engagements for SAP®, <Partner> Services uses a certified partner to perform the SAP® application installation and migration while <Partner>Services retain the infrastructure services. For the above reasons, this document makes no attempt to take the place of these SAP® document but to provide some general guidance related to the installation of SAP® systems on Azure. This document also utilizes existing intellectual property created by other organizations in Microsoft.

2 SAP® on Azure Deployment PlanningTo plan for SAP® running on Azure, the following documents detail all aspects of deployment planning.

1. SAP® NetWeaver on Azure Virtual Machines – Planning and Implementation Guide

2. SAP® NetWeaver on Azure Virtual Machines – Deployment Guide 3. SAP® DBMS in Azure Deployment Guide

The reader is recommended to download the above documents and review the provided guidance thoroughly before starting to install.

2

3 SAP® on Azure Installation RequirementsInstalling SAP® systems on Azure require the following resources

An Azure subscription and an Azure storage account SAP® Service Marketplace user account The Azure Infrastructure Build Guide (part of Azure Infrastructure for SAP® IP

Kit) Deploy Azure VMs per the Azure Infrastructure Build Guide Download and install the SAP® Download Manager on a utility VM acting as

file server hosting the many SAP® install media DVD images Install SAP®GUI on the utility VM if desire so it doesn’t have to be installed in

all SAP® servers Download SAP® Master Guide for the SAP® application of interest and get

the installation media list Download all necessary SAP® install DVDs and unpack them onto clearly

named folders on the utility server using tools appropriate for the file formats. For example, RAR, Zip, and SAP®CAR.

3

4 Before InstallationBefore starting to install SAP® on Azure, it’s helpful to have a holistic view of the environments to be deployed on Azure. This include all infrastructure support components and SAP® related deployment strategy as listed below:

- Azure Domain Controller, Active Directory (AD), and DNS, - Azure network design- SAP® systems hosts naming convention- SAP® System IDs (SID) and SAP® system numbers- SAP® agent strategy for monitoring- SAP® transport server identification- SAP® Diagnostic Agent instance location (typically on the Solution Manager)- SAP® System Landscape Directory (SLD) server

4

5 During InstallationThere are specific configuration choices in installation components of a SAP® system

5.1 SAP® SQL Server Database- SAP® SQL Database requires having LATIN1_GENERAL_CP850_BIN2 collation- Plan for data files, tlog files, tempdb depends on the SAP® application being

installed to optimize performance - The SAP® database EXPORT DVDs need to be copied to a locally attached

drive to avoid the SAP® installer not finding the file paths. Other SAP® DVDs can remain on network file share from the utility server

- In installing the SQL Server database engine, select only necessary components: SQL Data engine, Client tool connectivity, Client tool backward compatibility, and Management tool (optional)

5.2 SAP® Application Server and Central ServicesWhile installing SAP® application servers and Central Services, it’s ok to have both the SAP® and SQL executables reside on the C: drive to make the server all hosted on one vhd file. SAP® server page file size planning can be done with information on OSS note 1518419. The instruction on this note will yield smaller OS page file sizes than what the SAP® installer (SAP®Inst) prerequisite checker’s requirement. The checker’s warning can be ignored and the installation will move forward without issue. The completed installation will works without issue.

5.3 Sample SAP® ECC on Azure Installation To demonstrate the detailed steps in installing a foundational SAP® system (ECC), the instructions are included here for readers’ reference.

5