PACT SAP Prod to Azure Project

Azure Detailed Design

The descriptions of other companies products in this document, if any, are provided only as a convenience to you. Any such references should not be considered an
endorsement or support by BNW Consulting, and BNW Consulting cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended
as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers.
This deliverable is provided AS IS without warranty of any kind and BNW MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OTHERWISE.
All trademarks are the property of their respective companies.
Microsoft and Windows are either registered trademarks or trademarks of BNW Corporation in the United States and/or other countries, SAP is either a trademark or a
registered trademark of SAP AG Germany.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Page ii

Part I:
Part II:
1
2
3
4
5

2
3

Version Control.............................................................................................................................................................. 5
Document Sign-Off ........................................................................................................................................................ 5
Reference Documents ................................................................................................................................................... 6
Glossary of terms .......................................................................................................................................................... 6

2
3
4

QA to Replace Pre-Prod ................................................................................................................................................ 7

Target Landscape Overview .......................................................................................................................................... 8

2
3

Landscape Naming...................................................................................................................................................... 10
Virtual Machine Naming............................................................................................................................................... 10
Azure Resources Naming ............................................................................................................................................ 11

RDP Port ..................................................................................................................................................................... 12

Rename local administrator account ............................................................................................................................ 12

2
3
4
5
6

Windows Settings ........................................................................................................................................................ 13

2
3

Datacentre Replication for Azure ............................................................................................ 16

Database Replication to Azure .................................................................................................................................... 16

SAP Central Services Replication ................................................................................................................................ 16
SAP Application Servers Replication ........................................................................................................................... 16
SAP MaxDB Replication .............................................................................................................................................. 16
Azure Files Replication ................................................................................................................................................ 17
Other Replication Requirements .................................................................................................................................. 17

Part VIII:
1

Windows Installations .............................................................................................................. 13

Windows Release Information ..................................................................................................................................... 13

Part VII:
1

SAP Server Hardening .................................................................................................................... 12

Management Stations.................................................................................................................................................. 12

Part VI:
1

Naming Conventions ................................................................................................................ 10

Datacenter Naming...................................................................................................................................................... 10

Part V:
1

High-Level Summary .................................................................................................................. 7

SAP Azure Support Prerequisites .................................................................................................................................. 7

Part IV:
1

Information ........................................................................................................................................ 5

This Document .............................................................................................................................................................. 5

Part III:
1

Contents

Azure Design ............................................................................................................................. 18

Resource Group .......................................................................................................................................................... 18

Public IP Addresses .................................................................................................................................................... 18
Network Security Group............................................................................................................................................... 18

4
5
6
7
8
9

10

Virtual Network ............................................................................................................................................................ 19

Storage Accounts ........................................................................................................................................................ 20
Availability Sets ........................................................................................................................................................... 22
Virtual Machine Storage .............................................................................................................................................. 22
Virtual Machines .......................................................................................................................................................... 23
Azure Internal Load Balancers..................................................................................................................................... 29
Azure Resource Tagging......................................................................................................................................... 30

11

Part IX:
1
2
3

2
3
4
5
6
7
8
9

SQLSERVER Instance Design ................................................................................................. 31

SQLSERVER Instance and Database Installation........................................................................................................ 31

SQLSERVER Cluster Setup ........................................................................................................................................ 36
SQLServer Backup Strategy ........................................................................................................................................ 38

Part X:
1

Azure Backup Strategy............................................................................................................................................ 30

SAP System Design ........................................................................................................................ 39

SAP Instance Installation ............................................................................................................................................. 39

SAP Binaries ............................................................................................................................................................... 40
SAP Instance Numbers ............................................................................................................................................... 41
SAP Central Services (ASCS & JSCS) Cluster ............................................................................................................ 43
SAP System ................................................................................................................................................................ 47
WebDispatcher ............................................................................................................................................................ 51
SAP Utility\Interface Server ......................................................................................................................................... 52
SAP Printing ................................................................................................................................................................ 52
SAPTrans .................................................................................................................................................................... 52

Part II:
1

This Document

Version Control

Information

This document describes the PACTs SAP Prod to Azure projects Detailed Design to migrate all relevant SAP
systems.

Version

Owner

Description

0.1

30/03/2016

Darryl Rabbitt

Document Creation

1.1

07/04/2016

Darryl Rabbitt

Changed Design for QA to be same

as Prod.

1.0

1.1

Issue Date

Document Sign-Off

Version

03/04/2016

Darryl Rabbitt

Released for Draft Review

Updated Design where needed

from feedback.

07/04/2016

Darryl Rabbitt

Added Backup details

Date

Owner

Description

BNW Consulting | SAP Replatform - Detailed Design

Reference Documents

Microsoft SQL Server Version List

http://blogs.technet.com/b/dataplatforminsider/archive/2014/09/25/using-ssds-in-azure-vms-to-store-sqlserver-tempdb-and-buffer-pool-extensions.aspx
Using SAP on Azure Virtual Machines (VMs)

OSS Note 2015553 - SAP on Microsoft Azure: Support prerequisites

1966681 - Release planning for Microsoft SQL Server 2014

http://blogs.msdn.com/b/saponsqlserver/archive/2013/06/30/1-microsoft-private-cloud-solution-for-saphardware-network-amp-san.aspxhttp://blogs.msdn.com/b/saponsqlserver/archive/2013/06/30/6-microsoftprivate-cloud-solution-for-sap-configuration-of-cluster-shared-volumes-vhdx-disks-amp-luns.aspx
http://blogs.msdn.com/b/saponsqlserver/archive/2013/06/30/9-microsoft-private-cloud-solution-for-saplandscape-design.aspx

Glossary of terms

Term/Acronym

Description

BPM

Business Process Modelling

IaaS

Infrastructure as a service the provision of infrastructure (networking, SAN, virtualisation layer, and a
running Virtual Machine. Management of all of the infrastructure is the responsibility of the IaaS provider.

BPRE

PaaS
SAP

Sol Man
VM

PAM
SAV

CSV
PAS
SAS
.vhd

.vhdx

Business Process Reverse Engineer - a software component of SAP Solution Manager

Platform as a Service One level higher than IaaS, the software platform is provided as a service and
the PaaS provider takes responsibility for ensuring the platform is operational and the customer just
consumes the services and has no concern for the application platform underneath.
Software Suite manufactured by SAP AG Germany
SAP Solution Manager
Virtual Machine

Platform Availability Matrix

Software At Value

Cluster Shared Volume

Primary Application Server, first SAP instance installed in an SAP system

Secondary Application Server All subsequent SAP application servers installed after the PAS
Microsoft Format Virtual Hard Disk

Microsoft Format Virtual Hard Disk (v2)

BNW Consulting | SAP Replatform - Detailed Design

Part III:
1

High-Level Summary

SAP Azure Support Prerequisites

To run SAP in Azure in a fully supported state, SAP and Microsoft require that the Production SAP systems be deployed in the Hybrid-IT
scenario, where the Azure Virtual Networks are connected back to the customers enterprise network through the use of Site-to-Site VPN
or Azure ExpressRoute.
OSS Note 2015553 - SAP on Microsoft Azure: Support prerequisites

To ensure SAP systems support on Microsoft Azure Virtual Machine Services, the following prerequisites have to be met in order to
ensure full supportability and optimal performance:

Support contract prerequisites

When operating SAP production systems on Microsoft Azure Virtual Machine Services, you must have at a minimum Microsoft
Premier Support contract in place with Microsoft.

Monitoring prerequisites
Full support requires enabling built-in SAP monitors to retrieve information about configuration and resource utilization from the
underlying Azure infrastructure.

Network prerequisites

Network Security

For any SAP production system installed on Azure, it is required that you operate in Virtual Private Network(s) which
is/are connected to your datacenters with Azure site-to-site or ExpressRoute connectivity.
Network Performance
For productive and non-productive 3-tier deployments, where application servers and the database server reside on
separate Azure VM instances and communicate via network, it is required that all Azure VM instances are located in
the same Azure Affinity Group and the same Azure Virtual Private Network.
It is NOT supported at all to run an SAP Application Server layer and DBMS layer split between on-premise and
Azure. Both layers need to completely reside either on-premise or in Azure. It is also NOT at all supported to have
SAP instances split between on-premise and Azure. Per individual SAP system, the DBMS and all SAP application
instance(s) must be in the same location, either Azure or on-premise.

Storage prerequisites
1. Virtual Hard Disks (VHDs) representing VMs and volumes mounted to a VM need to be grouped into Azure Storage
Accounts.
2. VHDs which are mounted to a VM need to be located in the same Azure Storage Account with the VHD of the VM.
3. Only VMs from the Standard Tier are supported. No Basic Tier SLAs of Azure VMs are supported for SAP systems.

QA to Replace Pre-Prod

Currently On-Premise Pre-Prod exists to provide similar architecture to Production, but this system is not fully utilised as a Pre-Prod
system where only limited testing occurs.

This Design is based around having QA replace Pre-Prod for BAU and Pre-Prod will be used as a Sandbox testing for the Production
move with the intent of deleting Pre-Prod post go-live.
This will allow QA to fully function is a landscape similar to Production and guarantee that all changes going into Production have been
tested on similar architecture.
This also allows full DR testing scenarios.

Pre-Prod will only exist in Azure as a Sandbox landscape to verify that we can move Production to Azure. Once go-live is completed PreProd will be deleted.

BNW Consulting | SAP Replatform - Detailed Design

3.1

Target Landscape Overview

Production and Quality

Quality architecturally similar to Production but can be sized down.

*Central services is showing a single system, PACT will have 6 separate Central services Clusters

BNW Consulting | SAP Replatform - Detailed Design

3.2

Development

BNW Consulting | SAP Replatform - Detailed Design

Part IV:
1

Naming Conventions

Datacenter Naming

Datacentre abbreviation: <ADC>

Datacentre

Australia East (Sydney)

Australia South East (Melbourne)

Landscape Naming

Landscape

Development
QA
Pre-Production
Production

Naming Convention
SYD

MEL

Short Naming Convention

Mid Naming Convention

Long Naming Convention

QA

Quality

D
X

DEV

PREPRD \ PPRD

PROD

Development

Pre-Production
Production

Virtual Machine Naming

Max of 13chars

<ADC>SAP<Landscape>
Description
SAP SQL Server
SAP SCS Server
SAP APP Server
SAP Non-Prod Server
SAP Livecache Server
SAP Utility Server

3.1

Naming Convention
SAP<ADC>-<Landscape_Short>SQLXX
SAP<ADC>-<Landscape_Short >SCSXX
SAP<ADC>-<Landscape_Short >APPXX
SAP<ADC>-<Landscape_Short >XX
SAP<ADC>-<Landscape_Short >LCAXX
SAP<ADC>-<Landscape_Short >UTL

Cluster pairing

VMs that are in clusters will be named in such a way that it is easy to identify the cluster pairs. How this will occur is using a naming
convention where the first node numerical number has 50 added to it.
Eg, Cluster node SAPSYD-SCS01 the cluster pair will be called SAPSYD-SCS51

BNW Consulting | SAP Replatform - Detailed Design

10

Azure Resources Naming

This section refers to PACT Naming Standards 5.1 (draft)

Azure Resource

Naming Convention

Resource Group

<ADC>_SAP_<Landscape_Mid>

Availability set

ASET_<SAPSID\DBSID>_<SCS\SQL>

Storage Account
Load balancer

<adc>sap<Landscape_Mid><pre\lrs\grs>storXX

LB_<SAPSID\DBSID>_<SCS\SQL>

Load balancer Health Probe

<LoadBalancer>-HealthProbe

Load balancer Backend IP Pools

<LoadBalancer>-Backend

Load balancer Frontend IP

Load balancing rules (iLB End Point)

Network interface

BNW Consulting | SAP Replatform - Detailed Design

<LoadBalancer>-Frontend

<SAPSID\DBSID>_<PORT>
<hostname>-nicXX

11

Part V:
1

SAP Server Hardening

Management Stations

A dedicated SAP Management Station is required to administer the secured SAP system. The Management Station is a server outside
the SAP VLANs with special permission to Terminal Service to the SAP systems. The Management Station acts as a gateway or proxy
to allow access to the SAP systems.
Management Stations will be used to access and administer the SAP servers.

No direct access to the SAP Servers will be granted. All admins must log onto the Management server first.

Hostname

IP Address

SRV-MGT-AZ-P10
SRV-MGT-AZ-P11

RDP Port

The default Windows Terminal Services (RDP) port is 3389. By changing the RDP port on each server to a secret port, unauthorised
access to an SAP server is much more difficult.
The RDP port is to be changed to a non-standard port --XXX--

Rename local administrator account

The local Windows server administrator account name is well known administrator. It is recommended
to disable this account and create a new administrator account
This is done by default for Azure VMs.

BNW Consulting | SAP Replatform - Detailed Design

12

Part VI:
1

Windows Installations

Windows Release Information

Server

Release

Version

Rollup

Mode

SAP and SQL

Servers

Windows 2012R2 DataCenter

6.3 (Build 9600)

March Build

Full Gui

2.1

Windows Settings
Windows Time zone

Time zone for servers will be set to GMT+10.

Changing time zone as part of the migration will cause all scheduling in SAP to be incorrect and cause significant confusing with end
users using system reports.

2.2

Power Modes

2.3

Internet Explorer

Set Power Mode to High Performance

Internet explorer is to removed from all SAP servers. There is no valid reason to have IE on any production SAP server.
dism /online /disable-feature /featurename:Internet-Explorer-Optional-amd64

2.4

Netbios

1431619 - Disable Netbios over TCP/IP in Windows environments

Netbios to be disabled on all SAP Servers

2.5

Dynamic Port range

SAP uses ports in the 50000-59900 range so we need move the windows dynamic port range to start at 60000 for SAP Servers.
netsh int ipv4 set dynamicport tcp start=60000 numberofports=5536
netsh int ipv4 show dynamicport tcp

BNW Consulting | SAP Replatform - Detailed Design

13

2.6

TCP Chimney Offload

In the SAP environment, TCP Chimney Offload caused problems that resulted in sporadic connection breakdowns between the SAP
application servers and database servers. Therefore, TCP Chimney offload should remain disabled.
Verify TCP Chimney Offload is disabled
Netsh int tcp show global

2.7

Receive Side Scaling

RSS is able to distribute DPC handling of a single VMQ over multiple CPU threads on the host.
Enable RSS

Set Number of RSS queues to Auto

BNW Consulting | SAP Replatform - Detailed Design

14

2.8

Shared Folder fix

http://support2.microsoft.com/kb/2820470

$Key = "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkStation\Parameters"
If ( -Not ( Test-Path "Registry::$Key")){New-Item -Path "Registry::$Key" -ItemType RegistryKey -Force}
Set-ItemProperty -path "Registry::$Key" -Name "DisableCARetryOnInitialConnect" -Type "DWORD" -Value "1"

2.9

Windows Partition\Volume Setup

All additional disks will be created as GPT disks.

All Database Data and Log Volumes to be formatted with Allocation Unit Size of 64KB, all other SAP\SQLSERVER Volumes 4KB.

BNW Consulting | SAP Replatform - Detailed Design

15

Part VII:

Datacentre Replication for Azure

Database Replication to Azure

SAP Central Services Replication

SAP Application Servers Replication

SAP MaxDB Replication

Database layer to be replicated using SQLSERVER AlwaysON Availability Groups.

SAP Central Services to be replicated using SIOS

SAP Application Servers will not be replicated, these will be prebuilt in the DR Datacentre.

MaxDB databases will be replicated using MaxDB logroll.

BNW Consulting | SAP Replatform - Detailed Design

16

Azure Files Replication

Other Replication Requirements

Azure Files will be replicated via a Powershell script

Most other replication requirements will be handled via a Powershell script.

BNW Consulting | SAP Replatform - Detailed Design

17

Part VIII:
1

Azure Design

Resource Group

Resource Groups used to group SAP Azure Services

Resource Group

Location

SYD_SAP_PREPRD

Sydney

SYD_SAP_NONPROD

Sydney

MEL_SAP_PREPRD

Melbourne

SYD_SAP_PROD
SYD_SAP_QA

MEL_SAP_PROD
MEL_SAP_QA

Sydney

Sydney

Melbourne
Melbourne

Public IP Addresses

SAP has no requirement for Public IP Address.

All Public end points to be removed from SAP Virtual Machines.

Network Security Group

Do we want to use Network Security Groups to further isolate network traffic ?

Our preference is to use Windows Firewalls to control access to the Server, currently there is very little logging for Network Security
Groups.
Pact intends to utilise Barracuda Firewall Virtual Appliance within SYD/MELB Azure to provide extra layer of security.

BNW Consulting | SAP Replatform - Detailed Design

18

Virtual Network

Virtual Network Name to be used in Azure

vNet Name

PACTVNET_SYD_2
PACTVNET_MEL_1

4.1

Address Space

10.202.0.0/21

Resource Group

10.203.0.0/21

PACT_SYD_01 vNet Subnets

Subnets that will exist in the PACT_SYD_01 Virtual Network.

IP Range
10.202.4.128/25
10.202.4.0/25
10.202.3.0/24
10.100.8.0/24

Subnet Name
SAP-NonProd
SAP-Quality
SAP-Production
Management

Usage
SAP Non-Production
SAP Quality\Pre-Prod
SAP Production
Management Servers

4.2

PACTVNET_MEL_1 vNet Subnets

4.3

Routing

IP Range

Subnet Name
Subnet-1
SAP-Quality
SAP-Production
Management

Usage
Reserved
SAP Quality\Pre-Prod
SAP Production
Management Servers

All traffic will be forced down Express Route, this means we need to setup a local rule in the Routing table to direct all Azure URL traffic
directly to Azure. Otherwise traffic for Database Direct to Blob storage and Azure Files will route down ER then back up ER to Azure and
cause significant performance issues.
Add the following routes to the Routing table:

Description
Azure Blob Storage
Azure Files

Address
*.blob.core.windows.net
*.file.core.windows.net

BNW Consulting | SAP Replatform - Detailed Design

Next Hop
Internet
Internet

19

Storage Accounts

Best practice is to segregate SAP landscapes into different Storage Accounts to ensure IOPS is not limited.
Storage Accounts that will exist.

5.1

SYD_SAP Storage Accounts

Description

Type

sydsapdevlrsstor11

SAP Development SAP VMs

Standard SYD_SAP_NONPROD

Locally

sydsapdevbcklrsstor12

SAP Development Database Backups

Standard SYD_SAP_NONPROD

Locally

sydsapdevprmstor11

SAP Development Databases

Premium SYD_SAP_NONPROD

Locally

sydsapqalrsstor11

SAP QA SAP VMs

Standard SYD_SAP_QA

Locally

sydsapqabcklrsstor12

SAP QA Database Backups

Standard SYD_SAP_QA

Locally

sydsapqaprmstor11

SAP QA SQL Databases Node 1

Premium SYD_SAP_QA

Locally

sydsapqaprmstor12

SAP QA SQL Databases Node 2

Premium SYD_SAP_QA

Locally

sydsapqaprmstor13

SAP QA MaxDB Databases

Premium SYD_SAP_QA

Locally

sydsappprdlrsstor11

SAP Pre-Production SAP VMs

Standard SYD_SAP_PREPRD

Locally

sydsappprdbcklrsstor12

SAP Pre-Production Database Backups

Standard SYD_SAP_PREPRD

Locally

sydsappprdprmstor11

SAP Pre-Production SQL Databases Node 1

Premium SYD_SAP_PREPRD

Locally

sydsappprdprmstor12

SAP Pre-Production SQL Databases Node 2

Premium SYD_SAP_PREPRD

Locally

sydsappprdprmstor13

SAP Pre-Production MaxDB Databases

Premium SYD_SAP_PREPRD

Locally

sydsapprodlrsstor11

SAP Production SAP VMs

Standard SYD_SAP_PROD

Locally

sydsapprodbcklrsstor12

SAP Production Database Backups

Standard SYD_SAP_PROD

Locally

sydsapprodlrsstor13

SAPTrans Azure Files

Standard SYD_SAP_PROD

Locally

sydsapprodprmstor11

SAP Production SQL Databases Node 1

Premium SYD_SAP_PROD

Locally

sydsapprodprmstor12

SAP Production SQL Databases Node 2

Premium SYD_SAP_PROD

Locally

sydsapprodprmstor13

SAP Production MaxDB Databases

Premium SYD_SAP_PROD

Locally

sydsapmgtlrsstor11

SAP Management VMs

Standard SYD_SAP_MGT

Locally

Storage Account Name

BNW Consulting | SAP Replatform - Detailed Design

Resource Group

Redundancy

20

5.2

MEL_SAP Storage Accounts

Storage Account Name

melsapqalrsstor11

melsapqabcklrsstor12

Description

SAP QA SAP VMs

SAP QA Database Backups

Type

Resource Group

Redundancy

Standard

MEL_SAP_QA

Premium

MEL_SAP_QA

Locally

Standard

MEL_SAP_QA

Locally

Locally

melsapqaprmstor11

SAP QA SQL Databases Node 1

melsappprdlrsstor11

SAP Pre-Production SAP VMs

Standard

MEL_SAP_PREPRD

Locally

melsappprdprmstor11

SAP Pre-Production SQL Databases Node 1

Premium

MEL_SAP_PREPRD

Locally

melsapprodlrsstor11

SAP Production SAP VMs

Standard

MEL_SAP_PROD

Locally

melsapprodlrsstor12

SAPTrans Azure Files

melsapqaprmstor13

melsappprdbcklrsstor11
melsappprdprmstor13
melsapprodlrsstor11
melsapprodprmstor11
melsapprodprmstor13
melsapmgtlrsstor11

SAP QA MaxDB Databases

SAP Pre-Production tabase Backups

SAP Pre-Production MaxDB Databases

Premium

Standard

Premium

MEL_SAP_QA

MEL_SAP_PREPRD

MEL_SAP_PREPRD

Locally

Locally

Locally

SAP Production tabase Backups

Standard

MEL_SAP_PROD

SAP Production SQL Databases Node 1

Premium

MEL_SAP_PROD

Locally

SAP Management VMs

Standard

MEL_SAP_MGT

Locally

SAP Production MaxDB Databases

BNW Consulting | SAP Replatform - Detailed Design

Standard

Premium

MEL_SAP_PROD

MEL_SAP_PROD

Locally

Locally

Locally

21

Availability Sets

To ensure redundancy in Azure, Availability Sets will be used. This will force Azure to provision VMs in different Fault Domains and
Upgrade Domains.
Production Database VMs will exist in 1 Availability Set for each system.
Production SCS will exist in 1 Availability Set for each system.
Production Application VMs will exist 1 Availability Set
QA Database VMs will exist in 1 Availability Set.
QA SCS VMs will exist in 1 Availability Set.

QA Application VMs will exist in 1 Availability Set

Non Production VMs will exist in 1 Availability Set for each landscape, Eg 1 for Dev etc.

7.1

Virtual Machine Storage

Prod and QA SQL Servers

SQL servers have no requirement for additional storage.

SQL Instance will be directly installed on C: drive.
Database to be installed direct to Blob

7.2

Prod and QA SAP SCS Servers

SAP SCS servers will have 1 x 1TB vhd assigned for each system and the SCS instance to be installed on this drive.
SAP ERS will be installed on C: drive.

7.3

Prod and QA SAP Application Servers

7.4

Non-Prod SAP Servers

SAP Application Servers will have 1 x 1TB vhd assigned as E: drive, SAP Instance will be installed on this drive.

Non-Prod SAP Servers will have 1 x 1TB vhd assigned as E: drive, SAP Instance will be installed on this drive.
SQL to be installed on C: drive.

Database to be installed direct to Blob

7.5

MaxDB Servers

7.6

Other Servers

Servers hosting a MaxDB database to have a P10 vhd assigned to the VM and the database installed on this vhd

Other servers to have vhds assigned as required. Eg, SAP utility server for Interface, Archive directories.

BNW Consulting | SAP Replatform - Detailed Design

22

Virtual Machines

IP Addresses for SAP Virtual Machines in Azure will be set to Static IP Addresses.

8.1

8.1.1

Production
SYD_SAP

Hostname

SAPSYD-PSQL01
SAPSYD-PSQL51
SAPSYD-PSCS01
SAPSYD-PSCS02
SAPSYD-PSCS03
SAPSYD-PSCS04
SAPSYD-PSCS05
SAPSYD-PSCS06
SAPSYD-PSCS51
SAPSYD-PSCS52
SAPSYD-PSCS53
SAPSYD-PSCS54
SAPSYD-PSCS55
SAPSYD-PSCS56
SAPSYD-PAPP01
SAPSYD-PAPP02
SAPSYD-PAPP03
SAPSYD-PLCA01
SAPSYD-PUTL01

Description

Production SQL Node 01

Production SQL Node 02
Production SP1 SCS Node 01
Production HRP SCS Node 01
Production SCP SCS Node 01
Production POP SCS Node 01
Production BIP SCS Node 01
Production SMP SCS Node 01
Production SP1 SCS Node 02
Production HRP SCS Node 02
Production SCP SCS Node 02
Production POP SCS Node 02
Production BIP SCS Node 02
Production SMP SCS Node 02
Production SAP Application Server 01
Production SAP Application Server 02
Production SAP Application Server 03
Production LiveCache Server 01
Production Utility Server 01

BNW Consulting | SAP Replatform - Detailed Design

Primary Network Interface

sapsyd-psql01-nic1
sapsyd-psql51-nic1
sapsyd-pscs01-nic1
sapsyd-pscs02-nic1
sapsyd-pscs03-nic1
sapsyd-pscs04-nic1
sapsyd-pscs05-nic1
sapsyd-pscs06-nic1
sapsyd-pscs51-nic1
sapsyd-pscs52-nic1
sapsyd-pscs53-nic1
sapsyd-pscs54-nic1
sapsyd-pscs55-nic1
sapsyd-pscs56-nic1
sapsyd-papp01-nic1
sapsyd-papp02-nic1
sapsyd-papp03-nic1
sapsyd-plca01-nic1
sapsyd-putl01-nic1

IP Address

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

VM
Size
D14
D14
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
D14
D14
D14

DS11
A2

Resource Group

SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD
SYD_SAP_PROD

23

Availability Set

ASET_SAP_SQL
ASET_SAP_SQL
ASET_SP1_SCS
ASET_HRP_SCS
ASET_SCP_SCS
ASET_POP_SCS
ASET_BIP_SCS
ASET_SMP_SCS
ASET_SP1_SCS
ASET_HRP_SCS
ASET_SCP_SCS
ASET_POP_SCS
ASET_BIP_SCS
ASET_SMP_SCS
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_LCA
ASET_SAP_UTL

Storage Account

sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11

sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodlrsstor11
sydsapprodprmstor13
sydsapprodlrsstor11

8.1.2

MEL_SAP

Hostname

SAPMEL-PSQL01
SAPMEL-PSCS01
SAPMEL-PAPP01
SAPMEL-PAPP02
SAPMEL-PAPP03
SAPMEL-PLCA01
SAPMEL-PUTL01

Description

Production SQL DR Node 01

Production SCS DR Node 01
Production SAP Application Server 01
Production SAP Application Server 02
Production SAP Application Server 03
Production LiveCache Server 01
Production Utility Server 01

BNW Consulting | SAP Replatform - Detailed Design

Primary Network Interface

sapmel-psql01-nic1
sapmel-pscs01-nic1
sapmel-papp01-nic1
sapmel-papp02-nic1
sapmel-papp03-nic1
sapmel-plca01-nic1
sapmel-putl01-nic1

IP Address

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

VM
Size
D11
A5
D14
D14
D14

DS11
A2

Resource Group

MEL_SAP_PROD
MEL_SAP_PROD
MEL_SAP_PROD
MEL_SAP_PROD
MEL_SAP_PROD
MEL_SAP_PROD
MEL_SAP_PROD

24

Availability Set

ASET_SAP_SQL
ASET_SAP_SCS
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_LCA
ASET_SAP_UTL

Storage Account

melsapprodlrsstor11
melsapprodlrsstor11
melsapprodlrsstor11
melsapprodlrsstor11
melsapprodlrsstor11

melsapprodprmstor13
melsapprodlrsstor11

8.2

8.2.1

Pre-Production
SYD_SAP

Hostname

SAPSYD-XSQL01
SAPSYD-XSQL51
SAPSYD-XSCS01
SAPSYD-XSCS02
SAPSYD-XSCS03
SAPSYD-XSCS04
SAPSYD-XSCS05
SAPSYD-XSCS51
SAPSYD-XSCS52
SAPSYD-XSCS53
SAPSYD-XSCS54
SAPSYD-XSCS55
SAPSYD-XAPP01
SAPSYD-XAPP02
SAPSYD-XAPP03
SAPSYD-XLCA01
SAPSYD-XUTL01

Description

Pre-Prod SQL Node 01

Pre-Prod SQL Node 02
Pre-Prod SX1 SCS Node 01
Pre-Prod HRX SCS Node 01
Pre-Prod SCX SCS Node 01
Pre-Prod POX SCS Node 01
Pre-Prod BIX SCS Node 01
Pre-Prod SX1 SCS Node 02
Pre-Prod HRX SCS Node 02
Pre-Prod SCX SCS Node 02
Pre-Prod POX SCS Node 02
Pre-Prod BIX SCS Node 02
Pre-Prod SAP Application Server 01
Pre-Prod SAP Application Server 02
Pre-Prod SAP Application Server 03
Pre-Prod LiveCache Server 01
Pre-Prod Utility Server 01

BNW Consulting | SAP Replatform - Detailed Design

Primary Network Interface

sapsyd-xsql01-nic1
sapsyd-xsql51-nic1
sapsyd-xscs01-nic1
sapsyd-xscs02-nic1
sapsyd-xscs03-nic1
sapsyd-xscs04-nic1
sapsyd-xscs05-nic1
sapsyd-xscs51-nic1
sapsyd-xscs52-nic1
sapsyd-xscs53-nic1
sapsyd-xscs54-nic1
sapsyd-xscs55-nic1
sapsyd-xapp01-nic1
sapsyd-xapp02-nic1
sapsyd-xapp03-nic1
sapsyd-xlca01-nic1
sapsyd-xutl01-nic1

IP Address

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

VM
Size
D14
D14
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
D14
D14
D14

DS11
A2

Resource Group

SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD
SYD_SAP_PREPRD

25

Availability Set

ASET_SAP_SQL
ASET_SAP_SQL
ASET_SX1_SCS
ASET_HRX_SCS
ASET_SCX_SCS
ASET_POX_SCS
ASET_BIX_SCS
ASET_SX1_SCS
ASET_HRX_SCS
ASET_SCX_SCS
ASET_POX_SCS
ASET_BIX_SCS
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_LCA
ASET_SAP_UTL

Storage Account

sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11
sydsappprdlrsstor11

sydsappprdprmstor13
sydsappprdlrsstor11

8.2.2

MEL_SAP

Hostname

SAPMEL-XSQL01
SAPMEL-XSCS01
SAPMEL-XAPP01
SAPMEL-XAPP02
SAPMEL-XAPP03
SAPMEL-XLCA01
SAPMEL-XUTL01

Description

Pre-Prod SQL DR Node 01

Pre-Prod SCS DR Node 01
Pre-Prod SAP Application Server 01
Pre-Prod SAP Application Server 02
Pre-Prod SAP Application Server 03
Pre-Prod LiveCache Server 01
Pre-Prod Utility Server 01

BNW Consulting | SAP Replatform - Detailed Design

Primary Network Interface

sapmel-xsql01-nic1
sapmel-xscs01-nic1
sapmel-xapp01-nic1
sapmel-xapp02-nic1
sapmel-xapp03-nic1
sapmel-xlca01-nic1
sapmel-xutl01-nic1

IP Address

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

VM
Size
D11
A5
D14
D14
D14

DS11
A2

Resource Group

MEL_SAP_PREPRD
MEL_SAP_PREPRD
MEL_SAP_PREPRD
MEL_SAP_PREPRD
MEL_SAP_PREPRD
MEL_SAP_PREPRD
MEL_SAP_PREPRD

26

Availability Set

ASET_SAP_SQL
ASET_SAP_SCS
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_LCA
ASET_SAP_UTL

Storage Account

melsappprdlrsstor11
melsappprdlrsstor11
melsappprdlrsstor11
melsappprdlrsstor11
melsappprdlrsstor11

melsappprdprmstor13
melsappprdlrsstor11

8.3

8.3.1

QA
SYD_SAP

Hostname

SAPSYD-QSQL01
SAPSYD-QSQL51
SAPSYD-QSCS01
SAPSYD-QSCS02
SAPSYD-QSCS03
SAPSYD-QSCS04
SAPSYD-QSCS05
SAPSYD-QSCS51
SAPSYD-QSCS52
SAPSYD-QSCS53
SAPSYD-QSCS54
SAPSYD-QSCS55
SAPSYD-QAPP01
SAPSYD-QAPP02
SAPSYD-QLCA01
SAPSYD-QUTL01

Description

QA SQL Node 01
QA SQL Node 02
QA ST1 SCS Node 01
QA HRT SCS Node 01
QA SCT SCS Node 01
QA POT SCS Node 01
QA BIT SCS Node 01
QA ST1 SCS Node 02
QA HRT SCS Node 02
QA SCT SCS Node 02
QA POT SCS Node 02
QA BIT SCS Node 02
QA SAP Application Server 01
QA SAP Application Server 02
QA LiveCache Server 01
QA Utility Server 01

BNW Consulting | SAP Replatform - Detailed Design

Primary Network Interface

sapsyd-qsql01-nic1
sapsyd-qsql51-nic1
sapsyd-qscs01-nic1
sapsyd-qscs02-nic1
sapsyd-qscs03-nic1
sapsyd-qscs04-nic1
sapsyd-qscs05-nic1
sapsyd-qscs51-nic1
sapsyd-qscs52-nic1
sapsyd-qscs53-nic1
sapsyd-qscs54-nic1
sapsyd-qscs55-nic1
sapsyd-qapp01-nic1
sapsyd-qapp02-nic1
sapsyd-qlca01-nic1
sapsyd-qutl01-nic1

IP Address

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

VM
Size
D12
D12
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
D13
D13

DS11
A2

Resource Group
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA
SYD_SAP_QA

27

Availability Set

ASET_SAP_SQL
ASET_SAP_SQL
ASET_ST1_SCS
ASET_HRT_SCS
ASET_SCT_SCS
ASET_POT_SCS
ASET_BIQ_SCS
ASET_ST1_SCS
ASET_HRT_SCS
ASET_SCT_SCS
ASET_POT_SCS
ASET_BIQ_SCS
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_LCA
ASET_SAP_UTL

Storage Account

sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11
sydsapqalrsstor11

sydsapqaprmstor13
sydsapqalrsstor11

8.3.2

MEL_SAP

Hostname

SAPMEL-QSQL01
SAPMEL-QSCS01
SAPMEL-QAPP01
SAPMEL-QAPP02
SAPMEL-QLCA01
SAPMEL-QUTL01

8.4

Description

QA SQL DR Node 01
QA SCS DR Node 01
QA SAP Application Server 01
QA SAP Application Server 02
QA LiveCache Server 01
QA Utility Server 01

Primary Network Interface

sapmel-qsql01-nic1
sapmel-qscs01-nic1
sapmel-qapp01-nic1
sapmel-qapp02-nic1
sapmel-qlca01-nic1
sapmel-qutl01-nic1

IP Address

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

Development

Hostname

SAPSYD-DSQL01
SAPSYD-DAPP01
SAPSYD-DLCA01
SAPSYD-DUTL01

Description

Development SQL Server

Development SAP Instance Node
Development Livecache DB
Development Utility Server 01

BNW Consulting | SAP Replatform - Detailed Design

Primary Network Interface

sapsyd-dsql01-nic1
sapsyd-dapp01-nic1
sapsyd-dlca01-nic1
sapsyd-dutl01-nic1

IP Address

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

VM
Size
D11
A5
D13
D13

DS11
A2

VM
Size
D12
D12
DS11
A2

Resource Group
MEL_SAP_QA
MEL_SAP_QA
MEL_SAP_QA
MEL_SAP_QA
MEL_SAP_QA
MEL_SAP_QA

Resource Group

SYD_SAP_NONPROD
SYD_SAP_NONPROD
SYD_SAP_NONPROD
SYD_SAP_NONPROD

28

Availability Set

ASET_SAP_SQL
ASET_SAP_SCS
ASET_SAP_APP
ASET_SAP_APP
ASET_SAP_LCA
ASET_SAP_RTR

Availability
Set
ASET_DEV
ASET_DEV
ASET_DEV
ASET_DEV

Storage Account

melsapqalrsstor11
melsapqalrsstor11
melsapqalrsstor11
melsapqalrsstor11

melsapqaprmstor13
melsapqalrsstor11

Storage Account

sydsapdevlrsstor11
sydsapdevlrsstor11
sydsapdevlrsstor11
sydsapdevlrsstor11

8.5

SAP Enhanced Monitoring

1409604 Virtualization on Windows: Enhanced monitoring

SAP enhanced monitoring within a Microsoft Azure Virtual Machine is required to be activated on all SAP Virtual Machines.

Azure Internal Load Balancers

For High Availability to work in Azure you need to create Internal Load Balancers that the fabric uses to redirect traffic to the correct
server.

9.1

Production

Internal Load Balancer

SYD iLB Frontend IP Address

LB_HRP_SCS

X.X.X.X

LB_SCP_SCS

X.X.X.X

LB_POP_SCS

X.X.X.X

LB_BIP_SCS

X.X.X.X

LB_SMP_SCS

X.X.X.X

LB_SP1_SCS

9.2

Pre-Production

X.X.X.X

SYD iLB Backend Pools

X.X.X.X - sapsyd-pscs01-nic1
X.X.X.X - sapsyd-pscs51-nic1
X.X.X.X - sapsyd-pscs02-nic1
X.X.X.X - sapsyd-pscs52-nic1
X.X.X.X - sapsyd-pscs03-nic1
X.X.X.X - sapsyd-pscs53-nic1
X.X.X.X - sapsyd-pscs04-nic1
X.X.X.X - sapsyd-pscs54-nic1
X.X.X.X - sapsyd-pscs05-nic1
X.X.X.X - sapsyd-pscs55-nic1
X.X.X.X - sapsyd-pscs06-nic1
X.X.X.X - sapsyd-pscs56-nic1

Internal Load Balancer

SYD iLB Frontend IP Address

LB_HRX_SCS

X.X.X.X

LB_SCX_SCS

X.X.X.X

LB_POX_SCS

X.X.X.X

LB_BIX_SCS

X.X.X.X

X.X.X.X - sapsyd-xscs05-nic1
X.X.X.X - sapsyd-xscs55-nic1

Internal Load Balancer

SYD iLB Frontend IP Address

SYD iLB Backend Pools

LB_HRT_SCS

X.X.X.X

LB_SCT_SCS

X.X.X.X

LB_POT_SCS

X.X.X.X

LB_BIQ_SCS

X.X.X.X

LB_SX1_SCS

9.3

Quality

LB_ST1_SCS

X.X.X.X

X.X.X.X

BNW Consulting | SAP Replatform - Detailed Design

SYD iLB Backend Pools

X.X.X.X - sapsyd-xscs01-nic1
X.X.X.X - sapsyd-xscs51-nic1
X.X.X.X - sapsyd-xscs02-nic1
X.X.X.X - sapsyd-xscs52-nic1
X.X.X.X - sapsyd-xscs03-nic1
X.X.X.X - sapsyd-xscs53-nic1
X.X.X.X - sapsyd-xscs04-nic1
X.X.X.X - sapsyd-xscs54-nic1

X.X.X.X - sapsyd-qscs01-nic1
X.X.X.X - sapsyd-qscs51-nic1
X.X.X.X - sapsyd-qscs02-nic1
X.X.X.X - sapsyd-qscs52-nic1
X.X.X.X - sapsyd-qscs03-nic1
X.X.X.X - sapsyd-qscs53-nic1
X.X.X.X - sapsyd-qscs04-nic1
X.X.X.X - sapsyd-qscs54-nic1
X.X.X.X - sapsyd-qscs05-nic1
X.X.X.X - sapsyd-qscs55-nic1

29

10

Azure Resource Tagging

Following tags will be used, but not limited to:

DEV
QA

PREPROD
PROD

11

Azure Backup Strategy

Azure backups will adhere to current PACT Azure Backup strategy.

11.1 OS Backups

Use Azure Recovery Services to protect Azure VMs

11.2 File Backups

Use Azure Recovery Services to provide file system backups for the SAP Central Services and SAP Application servers.

11.3 SQL Backups

SQL Backups that are less than 1TB will backup directly to BLOB storage.
SQL Backups that are greater than 1TB will backup to remote server and then be shipped off to BLOB storage.

BNW Consulting | SAP Replatform - Detailed Design

30

Part IX:
1

SQLSERVER Instance Design

SQLSERVER Instance and Database Installation

SQLSERVER instance installation will be performed as per SAP Installation guides.

SQL Server:
For the installation of your SQL Server database software in a HA environment, use the installation guide for Installation of SQL Server in
an SAP Environment, which is available at:
http://service.sap.com/instguides -> Database Upgrades -> MS SQL Server

1.1

1.1.1

Release Information
SQLSERVER 2014

Microsoft SQL Release and Version that will be used:

Release: SQLSERVER 2014 SP1 CU5
Version: 12.00.4439

Microsoft SQL Server 2014 Service Pack 1 (SP1)

Cumulative Update 5 (CU5) for SQL Server 2014 Service Pack 1

1.2

AD Accounts and Groups

The following Service user accounts will be used to run SQLSERVER.

Service

User

SQL Server

SAPSQLServer<DBSID>

SQL Server Agent

SAPSQLAgent<DBSID>

SAPSQLServer<DBSID> Accounts are to be added to the following AD Group

Text

SQL Server Group

User

SAPSQLServer_Accounts

1.3

Transparent Data Encryption (TDE)

1.4

High Availability

Current Database are not encrypted, TDE to not be used at PACT

SQLSERVER High-Availability will be provided by using AlwaysON SYNC.

There is no requirement to provide High Availability in Azure if in DR mode.

1.5

Disaster Recovery

SQL SERVER Disaster Recovery will be provided by using AlwaysON with ASYNC updates to the Melbourne Azure Datacenter.

BNW Consulting | SAP Replatform - Detailed Design

31

1.6

AlwaysOn Listener

AlwaysON Listener will not be used by PACT due to all instances residing on a single server.
When multi iLB becomes available PACT should then consider using a Listener.

1.7

Windows Local Policies

Add the SQLServer AD Group to the following User Rights Assignments local Policy

Grant Lock Pages in Memory permission to group SAPSQLServer_Group

Grant Perform Volume Maintenance Tasks permission to group SAPSQLServer_Group

BNW Consulting | SAP Replatform - Detailed Design

32

1.8

Instance Installation

A Named Installation will be performed as per SAP Installation guides.

SQLSERVER instance to be installed under C: Drive.
Exception: A minimal install of the SQLSERVER Instance will be performed. Only the Database Engine Services and Management
Tools will be installed. SAP Does not require any other feature.

1.9

1.9.1

Instance Trace Settings

SQLSERVER 2014

The following trace flags will be set as per 1986775 Configuration Parameters for SQL Server 2014

-T617
-T1117
-T1118
-T2371
-T2562
-T2549
-T3226
-T9481

Revert a behaviour in SQL Servers Lock Manager

Proportional File Auto-Growth
Disabling TempDB multi-object extents
Changes to automatic update statistics
Faster CHECKDB runtime
Faster CHECKDB runtime
Suppress successful backup operation log entries
Enforce the old Cardinality Estimation algorithms

1.10 Memory Settings

Memory Mix and Max values will need to be defined as the SQLSERVER instance are running on a Virtual machine.
Min and Max to be set to VM RAM 10%

-XXX- Memory settings will need to be defined or each instance. Need to check current usage.

BNW Consulting | SAP Replatform - Detailed Design

33

1.11 Storage design

With SQLSERVER 2014 a new feature has been introduced that allows a a Database to store Datafiles and Tlog files directly on Blob
Storage. We will use this Direct to Blob feature to store the database.
TempDB and the Buffer Pool Extension will reside on the local non-persistent disk.

1.11.1 Storage Account Container Naming Convention

SQL Server 2014 containers for Azure Databases will be named as <dbsid>-database.
This will provide segregation for all databases.

1.11.2 TempDB Setup

With Azure D series virtual machines, the recommendation is to store TempDB on the Non-Persistent SSD Disk.
Naming convention for Non-Persistent TempDB folder: <DBSID>-TempDB

For non-BW SAP Database create 4 x 2GB TempDB Datafiles and 1 x 512MB TempDB Logfile

For BW SAP Database create 1 TempDB Datafile per CPU and 1 TempDB Logfile, sizing is dependent of BW Database size.
Naming convention for TempDB datafiles: TempDBdata<x>.mdf\ndf
Naming convention for TempDB logfile: TempDBlog<x>.ldf

BNW Consulting | SAP Replatform - Detailed Design

34

1.12 Buffer Pool Extensions

With SQLSERVER 2014 a new feature has been introduced that allows an additional Buffer Pool to exist on the filesystem. This Buffer
Pool Extension allows the Buffer Pool in memory to spill out into high performing disk.
With Azure the recommendation is to store the Buffer Pool Extension on the Non-Persistent SSD Disk in standard storage and a
dedicated persistent drive in premium storage.
Naming convention for Non-Persistent Buffer Pool Extension folder: <DBSID>-BufferPool
Buffer Pool Extension sizing. DB Buffer x 6

BNW Consulting | SAP Replatform - Detailed Design

35

2.1

SQLSERVER Cluster Setup

2.1.1

Hostnames and IP Addresses

Production
Description

Nodes

Cluster Name

Production SQLServer

SAPSYD-PSQL01
SAPSYD-PSQL51
SAPMEL-PSQL01

Cluster
Name IP
Address

SAPGEO-PCLU01

X.X.X.X

Description

Nodes

Cluster Name

Pre-Production SQLServer

SAPSYD-XSQL01
SAPSYD-XSQL51
SAPMEL-XSQL01

Cluster
Name IP
Address

SAPGEO-XCLU01

X.X.X.X

Description

Nodes

Cluster Name

Quality SQLServer

SAPSYD-QSQL01
SAPSYD-QSQL51
SAPMEL-QSQL01

Cluster
Name IP
Address

SAPGEO-QCLU01

X.X.X.X

2.1.2

2.1.3

Pre-Production

Quality

BNW Consulting | SAP Replatform - Detailed Design

36

2.2

2.2.1

Cluster Settings
Quorum

File Share Witness Quorum to be used where the File Share Witness is to reside in Azure.
Azure Sydney Servers to be configured with 1 vote each

Azure Melbourne Servers to be configured with 0 vote each

2.2.2

Parameters

Cluster parameters will be set to Relaxed settings as per Tuning Failover Cluster Network Thresholds

Windows Server 2012 and later:

Parameter

SameSubnetDelay
SameSubnetThreshold
CrossSubnetDelay
CrossSubnetThreshold

Fast Failover
(Default)
1 second
5 heartbeats
1 second
5 heartbeats

BNW Consulting | SAP Replatform - Detailed Design

Relaxed

Maximum

1 second
10 heartbeats
2 seconds
20 heartbeats

2 seconds
120 heartbeats
4 seconds
120 heartbeats

37

SQLServer Backup Strategy

Production Backups retained for 1 month

Non-Prod Backups retained for 1 month

Landscape
Production
Quality
Development

Full
Weekly
Weekly
Weekly

Diff
Daily
Daily
Daily

Tlog
10mins
1hr
30mins

BNW Consulting | SAP Replatform - Detailed Design

38

Part X:
1

SAP System Design

SAP Instance Installation

SAP installation will be performed as per System Copy Guide for SAP Systems Based on SAP NetWeaver Application Server <SAP
Stack> on Windows Using Software Provisioning Manager 1.0

1.1

AD Accounts and Groups

The following user accounts are required for SAP.

Text
SAP Admin account

SAP Service account

User
<sapsid>adm

SAPService<SAPSID>

Users are added to the following AD Group

Text
SAP Group

User
SAP_<SAPSID>_GlobalAdmin

BNW Consulting | SAP Replatform - Detailed Design

39

2.1

SAP Binaries

2.1.1

SAP Kernel
7.22EXT Kernel

The following SAP Kernel will be used for all systems based on NW7.31 and below:

2.1.2

7.22 EXT stack 100: SAPEXE_100-70000603.SAR & SAPEXEDB_100-70000602.SAR

7.42 Kernel

The following SAP Kernel will be used for all systems based on NW7.4:

2.2

7.42 stack 300: SAPEXE_300-20012222.SAR & SAPEXEDB_300-20012221.SAR

SAP IGS

The following SAP IGS will be used:

SAP IGS 7.20_EXT SP10 (igsexe_10-20007794.sar)

2.3

SAP IGS HELPER (igshelper_4-10010245.sar)

SAP CRYPTOLIB

The following SAPCRYPTOLIB will be used:

2.4

COMMONCRYPTOLIB 8 patch 8448 (SAPCRYPTOLIBP_8448-20011729.SAR)

SAP HostAgent

The following SAP HostAgent will be used:

2.5

SAP HOST AGENT 7.21 SP11 (SAPHOSTAGENT11_11-20009417.SAR)

SAP MMC

The following SAP MMC will be used:

2.6

SAP MMC 7.42 SP2 (SAP_MMC_2-20012056.MSI)

SAP JVM

The following patch versions will be used where required:

SAP JVM 4.1 SP59 (SAPJVM4_59-10009724.SAR)

SAP JVM 5.1 SP106 (SAPJVM5_106-10004442.SAR)

2.7

SAP JVM 6.1 SP87 (SAPJVM6_87-10006998.SAR)

SAP WEB DISPATCHER

The following Web Dispatcher version will be used:

SAP WEB DISPATCHER 7.42 SP325 (SAPWEBDISP_SP_325-80000043.SAR)

BNW Consulting | SAP Replatform - Detailed Design

40

3.1

SAP Instance Numbers

Production Instance Numbers

The Instance numbers for each System and Instance will be derived from the following table:

ASID

ERP

HR ECC
SRM
EP

BW

SolMan

3.2

SP1

JSID

HRP
SCP
BIP

POP

SMP

ASCS

AERS

01

51

00
02
04
05

50
52
54
55

JSCS

JERS

01

13

63

15

65

ASID

ERP

HR ECC
SRM
EP

BW

SX1

JSID

HRX
SCX
BIX

POX

ASCS

AERS

01

51

00
02
04

50
52
54

JSCS

JERS

EP

BW

04
05

App
Servers
00

13

63

02
13
04

Quality Instance Numbers

HR ECC
SRM

13

01

Quality Instance Numbers will be based on the Production Instance Numbers.

ERP

02

Pre-Production Instance Numbers

Pre-Production Instance Numbers will be based on the Production Instance Numbers.

3.3

App
Servers
00

ASID
ST1

JSID

HRT
SCT
BIQ

POT

ASCS

AERS

01

51

00
02
04

BNW Consulting | SAP Replatform - Detailed Design

50
52
54

JSCS

JERS

App
Servers
00
01

13

63

02
13
04

41

3.4

Non-Production Instance Numbers

ASCS and JSCS Instance numbers to be based off Production Instance numbers.

3.4.1
ERP

HR ECC
SRM
EP

BW

SolMan

Development

ASID
SD1

JSID

HRD
SCD
BID

SMD

ASCS
00

AERS

JSCS

01
POD

02
04
05

BNW Consulting | SAP Replatform - Detailed Design

JERS

App
Servers
30
31

13
15

32
33
34
35

42

4.1

SAP Central Services (ASCS & JSCS) Cluster

SAP SPOFs (Single Point of Failure) Services

The design of the SAP system is to only have SPOFs (Single Point of Failure) on the Cluster. The Primary Application Server (PAS) and
Secondary Application Servers (SAS) will reside on servers outside the Cluster.
SAP Components to be installed on the SCS Cluster Servers are:

ASCS (ABAP Message Server and Enqueue Server)

Enqueue Replication Server

JSCS (Java Message Server and Enqueue Server)

SAP Gateway

WebDispatcher

BNW Consulting | SAP Replatform - Detailed Design

43

4.1.1

SAP Gateway

SAP Gateway will be added to the ASCS system, for Java only systems the SAP Gateway will be added to the JSCS. This will allow
automatic failover for the SAP Gateway which removes the Gateway as a SPOF.
Setting up the SAP Gateway will be done as per OSS Note 1010990 - Configuring a Standalone Gateway in an HA ASCS instance
SAP Gateway (gwmon) commands can be found in OSS Note 64016 Using the SAP Gateway monitor GWMON

4.1.2

WebDispatcher

A WebDispatcher will be installed for each SAP System and will be made Highly Available by adding the WebDispatcher as a Service in
the SAP System HA Group.
The WebDispatcher will be installed by following OSS Note 1564222 How to install the SAP Web Dispatcher in a Microsoft Failover
Cluster?

BNW Consulting | SAP Replatform - Detailed Design

44

4.2

SCS Cluster Hostnames and IP Addresses

To provide High-Availability to the SAP Central Services layer in Azure you create a Load Balancer that tests
who is the active node for the cluster in a could service.

There is an Azure limitation of only 1 Load Balancer per Cloud service. To provide High-Availability for all SAP
Systems you need 2 SCS servers per SAP System

4.2.1

Production
Description

Nodes

Cluster Name

Production SP1 SAP SCS

SAPSYD-PSCS01
SAPSYD-PSCS51

SAPGEO-PCLU02

Production HRP SAP SCS

SAPSYD-PSCS02
SAPSYD-PSCS52

Cluster
Name IP
Address
X.X.X.X

SAPGEO-PCLU03

X.X.X.X

SAPGEO-PCLU04

X.X.X.X

SAPGEO-PCLU05

X.X.X.X

SAPGEO-PCLU06

X.X.X.X

SAPSYD-PSCS06
SAPSYD-PSCS56

SAPGEO-PCLU07

X.X.X.X

Description

Nodes

Cluster Name

Production SX1 SAP SCS

SAPSYD-XSCS01
SAPSYD-XSCS51

SAPGEO-XCLU02

Cluster
Name IP
Address

Production SCP SAP SCS

Production POP SAP SCS
Production BIP SAP SCS
Production SMP SAP SCS

4.2.2

SAPSYD-PSCS03
SAPSYD-PSCS53
SAPSYD-PSCS04
SAPSYD-PSCS54
SAPSYD-PSCS05
SAPSYD-PSCS55

Pre-Production

Production HRX SAP SCS

SAPSYD-XSCS02
SAPSYD-XSCS52

X.X.X.X

SAPGEO-XCLU03

X.X.X.X

SAPGEO-XCLU04

X.X.X.X

SAPGEO-XCLU05

X.X.X.X

SAPSYD-XSCS05
SAPSYD-XSCS55

SAPGEO-XCLU06

X.X.X.X

Description

Nodes

Cluster Name

Production ST1 SAP SCS

SAPSYD-TSCS01
SAPSYD-TSCS51

SAPGEO-TCLU02

Cluster
Name IP
Address

Production SCX SAP SCS

Production POX SAP SCS
Production BIX SAP SCS

4.2.3

SAPSYD-XSCS03
SAPSYD-XSCS53
SAPSYD-XSCS04
SAPSYD-XSCS54

Quality

Production HRT SAP SCS

Production SCT SAP SCS
Production POT SAP SCS
Production BIT SAP SCS

SAPSYD-TSCS02
SAPSYD-TSCS52
SAPSYD-TSCS03
SAPSYD-TSCS53
SAPSYD-TSCS04
SAPSYD-TSCS54
SAPSYD-TSCS05
SAPSYD-TSCS55

BNW Consulting | SAP Replatform - Detailed Design

X.X.X.X

SAPGEO-TCLU03

X.X.X.X

SAPGEO-TCLU04

X.X.X.X

SAPGEO-TCLU05

X.X.X.X

SAPGEO-TCLU06

X.X.X.X

45

4.3

4.3.1

Cluster Settings
Quorum

File Share Witness Quorum to be used where the File Share Witness is to reside in Azure Sydney.

4.3.2

Parameters

Cluster parameters will be set to Relaxed settings as per Tuning Failover Cluster Network Thresholds

Windows Server 2012 and later:

Parameter

SameSubnetDelay
SameSubnetThreshold
CrossSubnetDelay
CrossSubnetThreshold

4.4

Fast Failover
(Default)
1 second
5 heartbeats
1 second
5 heartbeats

Relaxed

Maximum

1 second
10 heartbeats
2 seconds
20 heartbeats

2 seconds
120 heartbeats
4 seconds
120 heartbeats

SIOS Licenses

There will be 11 SAP SCS Clusters that will require SIOS to replicate the storage between nodes. 6 for Prod and 5 for PreProd\QA.
Each cluster has 2 nodes so this will require 22 SIOS licenses.

PreProd and QA will use the same license as QA will replace PreProd post go-live.

BNW Consulting | SAP Replatform - Detailed Design

46

5.1

SAP System

5.1.1

Production
SAP Central Services

SAP
System

SCS Virtual Host

(Client Access Point)

SP1
BIP
SCP
HRP
POP
SMP

5.1.2

SAPGEO-PSP1
SAPGEO-PHRP
SAPGEO-PSCP
SAPGEO-PPOP
SAPGEO-PBIP
SAPGEO-PSMP

SAPSYD-PAPP01
SAPSYD-PAPP02
SAPSYD-PAPP03
SAPMEL-PAPP01
SAPMEL-PAPP02
SAPMEL-PAPP03

SP1
BIP
SCP
HRP
POP
SMP

Description

App Server 1
App Server 2
App Server 3
DR App Server 1
DR App Server 2
DR App Server 3

SAP User Network

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

Hostname

SAPSYD-PAPP01
SAPSYD-PAPP02
SAPSYD-PAPP03
SAPSYD-PAPP02
SAPSYD-PAPP01
SAPSYD-PAPP03

Livecache Servers

SAP System
LCP

SAPSP1
SAPHRP
SAPSCP
SAPPOP
SAPBIP
SAPSMP

Primary Application Servers

SAP System

5.1.4

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

DNS Alias

SAP Application Servers

Hostname

5.1.3

SAP User Network

Hostname

SAPSYD-PLCA

BNW Consulting | SAP Replatform - Detailed Design

47

5.2

5.2.1

Pre-Production
SAP Central Services

SAP System
SX1
BIX
SCX
HRX
POX

5.2.2

SCS Virtual Host

(Client Access Point)
SAPGEO-PSX1
SAPGEO-PHRX
SAPGEO-PSCX
SAPGEO-PPOX
SAPGEO-PBIX

SAPSYD-XAPP01
SAPSYD-XAPP02
SAPSYD-XAPP03
SAPMEL-XAPP01
SAPMEL-XAPP02
SAPMEL-XAPP03

SX1
BIX
SCX
HRX
POX

Description

App Server 1
App Server 2
App Server 3
DR App Server 1
DR App Server 2
DR App Server 3

SAP User Network

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

Hostname

SAPSYD-XAPP01
SAPSYD-XAPP02
SAPSYD-XAPP03
SAPSYD-XAPP02
SAPSYD-XAPP01

Livecache Servers

SAP System
LCX

SAPSX1
SAPHRX
SAPSCX
SAPPOX
SAPBIX

Primary Application Servers

SAP System

5.2.4

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

DNS Alias

SAP Application Servers

Hostname

5.2.3

SAP User Network

Hostname

SAPSYD-XLCA

BNW Consulting | SAP Replatform - Detailed Design

48

5.3

5.3.1

Quality
SAP Central Services

SAP System
ST1
BIQ
SCT
HRT
POT

5.3.2

SCS Virtual Host

(Client Access Point)
SAPGEO-PST1
SAPGEO-PHRT
SAPGEO-PSCT
SAPGEO-PPOT
SAPGEO-PBIQ

SAPSYD-TAPP01
SAPSYD-TAPP02
SAPMEL-TAPP01
SAPMEL-TAPP02

ST1
BIQ
SCT
HRT
POT

Description

SAP User Network

App Server 1
App Server 2
DR App Server 1
DR App Server 2

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

Hostname

SAPSYD-TAPP01
SAPSYD-TAPP02
SAPSYD-TAPP01
SAPSYD-TAPP02
SAPSYD-TAPP01

IP Address

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

Livecache Servers

SAP System
LCT

SAPST1
SAPHRT
SAPSCT
SAPPOT
SAPBIQ

Primary Application Servers

SAP System

5.3.4

X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

DNS Alias

SAP Application Servers

Hostname

5.3.3

SAP User Network

Hostname

SAPSYD-TLCA

IP Address

X.X.X.X

BNW Consulting | SAP Replatform - Detailed Design

49

5.4

Development

SAP System
SD1
HRD
SCD
POD
BID
SMD
Livecache

Description

SD1 Development
HRD Development
SCD Development
POD Development
BID Development
SMD Development
Livecache Development

Hostname

SAPSYD-DAPP1
SAPSYD-DAPP1
SAPSYD-DAPP1
SAPSYD-DAPP1
SAPSYD-DAPP1
SAPSYD-DAPP1
SAPSYD-DLCA1

BNW Consulting | SAP Replatform - Detailed Design

IP
Address
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X
X.X.X.X

DNS Alias

SAPSD1
SAPHRD
SAPSCD
SAPPOD
SAPBID
SAPSMD

50

WebDispatcher

The WebDispatcher will be installed by following OSS Note 1564222 How to install the SAP Web Dispatcher in a Microsoft Failover
Cluster?

6.1

WebDispatcher Naming Convention

The naming of the WebDispatcher will be as follows:

First Letter:

Second Letter:

SAP System Type using the following values:

P Production

X Pre-Production
D Development
Q QA

C - Consolidation
T Training
Third Letter:

6.2

S Sandpit

Instance number loosely based on the table in section Production Instance Numbers

Production WebDispatcher

A WebDispatcher will be installed for each system using the table below.
Message Server
Instance Nr
SP1

00

SCP

02

BIP

04

HRP

01

POP

13

SMP

05

6.3

WebDispatcher
SID

WebDispatcher
Inst_Nr

WP1

71

8201

73

8213

75

8205

WP0
WP2
WP3
WP4
WP5

70

WebDispatcher
icm http port
8200

72

8202

74

8204

Pre-Production WebDispatcher

WebDispatcher will be installed for each system.

Pre-Production WebDispatcher Instance Numbers will be based off the Production WebDispatcher Table but using the Pre-Production
SAPSIDs.

6.4

Non-Production WebDispatcher

WebDispatcher will be installed for each Non-Prod system.

Non-Production WebDispatcher Instance Numbers will be based off the Production WebDispatcher Table but using the Non-Production
SAPSIDs.

BNW Consulting | SAP Replatform - Detailed Design

51

SAP Utility\Interface Server

PACT have a requirement for a SAP Utility Server. There is a user requirement to provide HA for the Utility Server in Azure.
This server will host the following components:

Host SAPRouter
Host the SAP custom Temporary working area. Eg, RP1 share
Host Sky software
Jellco palletiser

Synchronisation scripts for Azure files will also run on the utility server.

SAP Printing

Print devices are created directly on all app servers.

This is not best practice but is required due to custom code.

SAPTrans

SAPTrans will be hosted on Azure Files

This will provide a Highly-Available SAPTrans with triple redundancy without the requirement for an additional Virtual Machine.
All SAP Servers will have access to the SAPTrans share.

BNW Consulting | SAP Replatform - Detailed Design

52