Sie sind auf Seite 1von 52
PACT SAP Prod to Azure Project Azure Detailed Design
PACT SAP Prod to Azure Project Azure Detailed Design

PACT SAP Prod to Azure Project

Azure Detailed Design

The descriptions of other companies’ products in this document, if any, are provided only as

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.

The names of actual companies and products mentioned herein may be the trademarks of their respective
Part I: Contents Part II: Information 5 1 This Document 5 2 Version Control 5
Part I:
Contents
Part
II:
Information
5
1
This Document
5
2
Version Control
5
3
Document
Sign-Off
5
4
Reference Documents
6
5
Glossary of terms
6
Part
III:
High-Level Summary
7
1
SAP Azure Support Prerequisites
7
2
QA to Replace Pre-Prod
7
3
Target Landscape Overview
8
Part
IV:
Naming Conventions
10
1
Datacenter Naming
10
2
Landscape Naming
10
3
Virtual Machine Naming
10
4
Azure Resources Naming
11
Part V:
SAP Server Hardening
12
1
Management Stations
12
2
RDP Port
12
3
Rename local administrator account
12
Part
VI:
Windows Installations
13
1
Windows Release Information
13
2
Windows Settings
13
Part
VII:
Datacentre Replication for Azure
16
1
Database Replication to Azure
16
2
SAP Central Services Replication
16
3
SAP Application Servers Replication
16
4
SAP MaxDB Replication
16
5
Azure Files Replication
17
6
Other Replication Requirements
17
Part
VIII:
Azure Design
18
1 Resource Group
18
2 Public IP Addresses
18
3 Network Security Group
18

4

Virtual Network

19

5 Storage Accounts 20 6 Availability Sets 22 7 Virtual Machine Storage 22 8 Virtual
5
Storage Accounts
20
6
Availability Sets
22
7
Virtual Machine Storage
22
8
Virtual Machines
23
9
Azure Internal Load Balancers
29
10
Azure Resource Tagging
30
11
Azure Backup Strategy
30
Part
IX:
SQLSERVER Instance Design
31
1
SQLSERVER Instance and Database Installation
31
2
SQLSERVER
Cluster Setup
36
3
SQLServer Backup Strategy
38
Part X:
SAP System Design
39
1
SAP Instance Installation
39
2
SAP Binaries
40
3
SAP Instance Numbers
41
4
SAP Central Services (ASCS & JSCS) Cluster
43
5
SAP System
47
6
WebDispatcher
51
7
SAP Utility\Interface Server
52
8
SAP Printing
52
9
SAPTrans
52

Part II:

1 This Document

Information

This document describes the PACT’s SAP Prod to Azure project’s Detailed Design to migrate all relevant SAP systems.

2 Version Control Version Issue Date Owner Description 0.1 30/03/2016 Darryl Rabbitt Document Creation 1.0
2 Version Control
Version
Issue Date
Owner
Description
0.1
30/03/2016
Darryl Rabbitt
Document Creation
1.0
03/04/2016
Darryl Rabbitt
Released for Draft Review
1.1
07/04/2016
Darryl Rabbitt
Changed Design for QA to be same
as Prod.
Updated Design where needed
from feedback.
1.1
07/04/2016
Darryl Rabbitt
Added Backup details
3 Document Sign-Off
Version
Date
Owner
Description

4

Reference Documents

Microsoft SQL Server Version List

http://blogs.technet.com/b/dataplatforminsider/archive/2014/09/25/using-ssds-in-azure-vms-to-store-sql-

server-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

private-cloud-solution-for-sap-configuration-of-cluster-shared-volumes-vhdx-disks-amp-luns.aspx landscape-design.aspx 5
private-cloud-solution-for-sap-configuration-of-cluster-shared-volumes-vhdx-disks-amp-luns.aspx
landscape-design.aspx
5 Glossary of terms
Term/Acronym
Description
BPM
Business Process Modelling
BPRE
Business Process Reverse Engineer - a software component of SAP Solution Manager
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.
PaaS
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.
SAP
Software Suite manufactured by SAP AG Germany
Sol Man
SAP Solution Manager
VM
Virtual Machine
PAM
Platform Availability Matrix
SAV
Software At Value
CSV
Cluster Shared Volume
PAS
Primary Application Server, first SAP instance installed in an SAP system
SAS
Secondary Application Server – All subsequent SAP application servers installed after the PAS
.vhd
Microsoft Format Virtual Hard Disk
.vhdx
Microsoft Format Virtual Hard Disk (v2)

http://blogs.msdn.com/b/saponsqlserver/archive/2013/06/30/1-microsoft-private-cloud-solution-for-sap-

hardware-network-amp-san.aspxhttp://blogs.msdn.com/b/saponsqlserver/archive/2013/06/30/6-microsoft-

http://blogs.msdn.com/b/saponsqlserver/archive/2013/06/30/9-microsoft-private-cloud-solution-for-sap-

Part III:

High-Level Summary

1 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 customer’s 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
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.
2
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 Pre- Prod will be deleted.

3

Target Landscape Overview

3.1 Production and Quality

Quality architecturally similar to Production but can be sized down.

architecturally similar to Production but can be sized down. *Central services is showing a single system,
architecturally similar to Production but can be sized down. *Central services is showing a single system,

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

3.2

Development

3.2 Development BNW Consulting | SAP Replatform - Detailed Design 9

Part IV:

Naming Conventions

1 Datacenter Naming

Datacentre abbreviation: <ADC>

Datacentre Naming Convention Australia East (Sydney) SYD Australia South East (Melbourne) MEL 2 Landscape Naming
Datacentre
Naming Convention
Australia East (Sydney)
SYD
Australia South East (Melbourne)
MEL
2 Landscape Naming
Landscape
Short Naming Convention
Mid Naming Convention
Long Naming Convention
Development
D
DEV
Development
QA
Q
QA
Quality
Pre-Production
X
PREPRD \ PPRD
Pre-Production
Production
P
PROD
Production
3 Virtual Machine Naming
Max of 13chars
<ADC>SAP<Landscape>
Description
Naming Convention
SAP SQL Server
SAP<ADC>-<Landscape_Short>SQLXX
SAP SCS Server
SAP<ADC>-<Landscape_Short >SCSXX
SAP APP Server
SAP<ADC>-<Landscape_Short >APPXX
SAP Non-Prod Server
SAP<ADC>-<Landscape_Short >XX
SAP Livecache Server
SAP<ADC>-<Landscape_Short >LCAXX
SAP Utility Server
SAP<ADC>-<Landscape_Short >UTL
3.1 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

4

Azure Resources Naming

This section refers to PACT Naming Standards 5.1 (draft) Azure Resource Naming Convention Resource Group
This section refers to PACT Naming Standards 5.1 (draft)
Azure Resource
Naming Convention
Resource Group
<ADC>_SAP_<Landscape_Mid>
Storage Account
<adc>sap<Landscape_Mid><pre\lrs\grs>storXX
Availability set
ASET_<SAPSID\DBSID>_<SCS\SQL>
Load balancer
LB_<SAPSID\DBSID>_<SCS\SQL>
Load balancer Health Probe
<LoadBalancer>-HealthProbe
Load balancer Frontend IP
<LoadBalancer>-Frontend
Load balancer Backend IP Pools
<LoadBalancer>-Backend
Load balancing rules (iLB End Point)
<SAPSID\DBSID>_<PORT>
Network interface
<hostname>-nicXX

Part V:

SAP Server Hardening

1 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
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
2 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--
3 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.

Part VI:

Windows Installations

1 Windows Release Information

Server Release Version Rollup Mode SAP and SQL Servers Windows 2012R2 DataCenter 6.3 (Build 9600)
Server
Release
Version
Rollup
Mode
SAP and SQL
Servers
Windows 2012R2 DataCenter
6.3 (Build 9600)
March Build
Full Gui
2
Windows Settings
2.1
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
Set Power Mode to High Performance
2.3
Internet Explorer
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

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
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
2.8 Shared Folder fix http://support2.microsoft.com/kb/2820470 $Key =
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.

Part VII: Datacentre Replication for Azure

1 Database Replication to Azure

Database layer to be replicated using SQLSERVER AlwaysON Availability Groups.

be replicated using SQLSERVER AlwaysON Availability Groups. 2 SAP Central Services Replication SAP Central Services to
be replicated using SQLSERVER AlwaysON Availability Groups. 2 SAP Central Services Replication SAP Central Services to

2

SAP Central Services Replication

SAP Central Services to be replicated using SIOS

Replication SAP Central Services to be replicated using SIOS 3 SAP Application Servers Replication SAP Application

3 SAP Application Servers Replication

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

4 SAP MaxDB Replication

MaxDB databases will be replicated using MaxDB logroll.

5

Azure Files Replication

Azure Files will be replicated via a Powershell script

6 Other Replication Requirements

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

replication requirements will be handled via a Powershell script. BNW Consulting | SAP Replatform - Detailed

Part VIII:

Azure Design

1 Resource Group

Resource Groups used to group SAP Azure Services

Resource Group Location SYD_SAP_PROD Sydney SYD_SAP_PREPRD Sydney SYD_SAP_QA Sydney SYD_SAP_NONPROD Sydney
Resource Group
Location
SYD_SAP_PROD
Sydney
SYD_SAP_PREPRD
Sydney
SYD_SAP_QA
Sydney
SYD_SAP_NONPROD
Sydney
MEL_SAP_PROD
Melbourne
MEL_SAP_PREPRD
Melbourne
MEL_SAP_QA
Melbourne
2 Public IP Addresses
SAP has no requirement for Public IP Address.
All Public end points to be removed from SAP Virtual Machines.
3 Network Security Group
Do we want to use Network Security Groups to further isolate network traffic ?
Pact intends to utilise Barracuda Firewall Virtual Appliance within SYD/MELB Azure to provide extra layer of security.

Our preference is to use Windows Firewalls to control access to the Server, currently there is very little logging for Network Security Groups.

4

Virtual Network

Virtual Network Name to be used in Azure

vNet Name Address Space Resource Group PACTVNET_SYD_2 10.202.0.0/21 PACTVNET_MEL_1 10.203.0.0/21 4.1 PACT_SYD_01
vNet Name
Address Space
Resource Group
PACTVNET_SYD_2
10.202.0.0/21
PACTVNET_MEL_1
10.203.0.0/21
4.1
PACT_SYD_01 vNet Subnets
Subnets that will exist in the PACT_SYD_01 Virtual Network.
IP Range
Subnet Name
Usage
10.202.4.128/25
SAP-NonProd
SAP Non-Production
10.202.4.0/25
SAP-Quality
SAP Quality\Pre-Prod
10.202.3.0/24
SAP-Production
SAP Production
10.100.8.0/24
Management
Management Servers
4.2 PACTVNET_MEL_1 vNet Subnets
IP Range
Subnet Name
Usage
Subnet-1
Reserved
SAP-Quality
SAP Quality\Pre-Prod
SAP-Production
SAP Production
Management
Management Servers
4.3 Routing
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
Address
Next Hop
Azure Blob Storage
*.blob.core.windows.net
Internet
Azure Files
*.file.core.windows.net
Internet

5

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 Resource Group Redundancy Storage Account Name sydsapdevlrsstor11 SAP Development SAP VMs Standard
Description
Type
Resource Group
Redundancy
Storage Account Name
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

5.2

MEL_SAP Storage Accounts

Storage Account Name Description Type Resource Group Redundancy melsapqalrsstor11 SAP QA SAP VMs Standard
Storage Account Name
Description
Type
Resource Group
Redundancy
melsapqalrsstor11
SAP QA SAP VMs
Standard
MEL_SAP_QA
Locally
melsapqabcklrsstor12
SAP QA Database Backups
Standard
MEL_SAP_QA
Locally
melsapqaprmstor11
SAP QA SQL Databases Node 1
Premium
MEL_SAP_QA
Locally
melsapqaprmstor13
SAP QA MaxDB Databases
Premium
MEL_SAP_QA
Locally
melsappprdlrsstor11
SAP Pre-Production SAP VMs
Standard
MEL_SAP_PREPRD
Locally
melsappprdbcklrsstor11
SAP Pre-Production tabase Backups
Standard
MEL_SAP_PREPRD
Locally
melsappprdprmstor11
SAP Pre-Production SQL Databases Node 1
Premium
MEL_SAP_PREPRD
Locally
melsappprdprmstor13
SAP Pre-Production MaxDB Databases
Premium
MEL_SAP_PREPRD
Locally
melsapprodlrsstor11
SAP Production SAP VMs
Standard
MEL_SAP_PROD
Locally
melsapprodlrsstor11
SAP Production tabase Backups
Standard
MEL_SAP_PROD
Locally
melsapprodlrsstor12
SAPTrans Azure Files
Standard
MEL_SAP_PROD
Locally
melsapprodprmstor11
SAP Production SQL Databases Node 1
Premium
MEL_SAP_PROD
Locally
melsapprodprmstor13
SAP Production MaxDB Databases
Premium
MEL_SAP_PROD
Locally
melsapmgtlrsstor11
SAP Management VMs
Standard
MEL_SAP_MGT
Locally

6

Availability Sets

To ensure redundancy in Azure, Availability Sets will be used. This will force Azure to provision VM’s in different Fault Domains and Upgrade Domains.

Production Database VM’s 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 VM’s will exist in 1 Availability Set.

QA SCS VMs will exist in 1 Availability Set. QA Application VMs will exist in
QA SCS VMs will exist in 1 Availability Set.
QA Application VMs will exist in 1 Availability Set
Non Production VM’s will exist in 1 Availability Set for each landscape, Eg 1 for Dev etc.
7
Virtual Machine Storage
7.1
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
SAP Application Servers will have 1 x 1TB vhd assigned as E: drive, SAP Instance will be installed on this drive.
7.4
Non-Prod SAP Servers
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

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

7.6 Other Servers

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

8 Virtual Machines IP Addresses for SAP Virtual Machines in Azure will be set to
8
Virtual Machines
IP Addresses for SAP Virtual Machines in Azure will be set to Static IP Addresses.
8.1
Production
8.1.1
SYD_SAP
VM
Hostname
Description
Primary Network Interface
IP Address
Resource Group
Availability Set
Storage Account
Size
SAPSYD-PSQL01
Production SQL Node 01
sapsyd-psql01-nic1
X.X.X.X
D14
SYD_SAP_PROD
ASET_SAP_SQL
sydsapprodlrsstor11
SAPSYD-PSQL51
Production SQL Node 02
sapsyd-psql51-nic1
X.X.X.X
D14
SYD_SAP_PROD
ASET_SAP_SQL
sydsapprodlrsstor11
SAPSYD-PSCS01
Production SP1 SCS Node 01
sapsyd-pscs01-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_SP1_SCS
sydsapprodlrsstor11
sydsapprodlrsstor11
SAPSYD-PSCS02
Production HRP SCS Node 01
sapsyd-pscs02-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_HRP_SCS
SAPSYD-PSCS03
Production SCP SCS Node 01
sapsyd-pscs03-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_SCP_SCS
sydsapprodlrsstor11
SAPSYD-PSCS04
Production POP SCS Node 01
sapsyd-pscs04-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_POP_SCS
sydsapprodlrsstor11
sapsyd-pscs05-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_BIP_SCS
sydsapprodlrsstor11
SAPSYD-PSCS05
Production BIP SCS Node 01
SAPSYD-PSCS06
Production SMP SCS Node 01
sapsyd-pscs06-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_SMP_SCS
sydsapprodlrsstor11
SAPSYD-PSCS51
Production SP1 SCS Node 02
sapsyd-pscs51-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_SP1_SCS
sydsapprodlrsstor11
SAPSYD-PSCS52
Production HRP SCS Node 02
sapsyd-pscs52-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_HRP_SCS
sydsapprodlrsstor11
SAPSYD-PSCS53
Production SCP SCS Node 02
sapsyd-pscs53-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_SCP_SCS
sydsapprodlrsstor11
SAPSYD-PSCS54
Production POP SCS Node 02
sapsyd-pscs54-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_POP_SCS
sydsapprodlrsstor11
SAPSYD-PSCS55
Production BIP SCS Node 02
sapsyd-pscs55-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_BIP_SCS
sydsapprodlrsstor11
SAPSYD-PSCS56
Production SMP SCS Node 02
sapsyd-pscs56-nic1
X.X.X.X
A5
SYD_SAP_PROD
ASET_SMP_SCS
sydsapprodlrsstor11
SAPSYD-PAPP01
Production SAP Application Server 01
sapsyd-papp01-nic1
X.X.X.X
D14
SYD_SAP_PROD
ASET_SAP_APP
sydsapprodlrsstor11
SAPSYD-PAPP02
Production SAP Application Server 02
sapsyd-papp02-nic1
X.X.X.X
D14
SYD_SAP_PROD
ASET_SAP_APP
sydsapprodlrsstor11
SAPSYD-PAPP03
Production SAP Application Server 03
sapsyd-papp03-nic1
X.X.X.X
D14
SYD_SAP_PROD
ASET_SAP_APP
sydsapprodlrsstor11
SAPSYD-PLCA01
Production LiveCache Server 01
sapsyd-plca01-nic1
X.X.X.X
DS11
SYD_SAP_PROD
ASET_SAP_LCA
sydsapprodprmstor13
SAPSYD-PUTL01
Production Utility Server 01
sapsyd-putl01-nic1
X.X.X.X
A2
SYD_SAP_PROD
ASET_SAP_UTL
sydsapprodlrsstor11
BNW Consulting | SAP Replatform - Detailed Design
23

8.1.2

MEL_SAP

VM Hostname Description Primary Network Interface IP Address Resource Group Availability Set Storage Account Size
VM
Hostname
Description
Primary Network Interface
IP Address
Resource Group
Availability Set
Storage Account
Size
SAPMEL-PSQL01
Production SQL DR Node 01
sapmel-psql01-nic1
X.X.X.X
D11
MEL_SAP_PROD
ASET_SAP_SQL
melsapprodlrsstor11
SAPMEL-PSCS01
Production SCS DR Node 01
sapmel-pscs01-nic1
X.X.X.X
A5
MEL_SAP_PROD
ASET_SAP_SCS
melsapprodlrsstor11
Production SAP Application Server 01
sapmel-papp01-nic1
X.X.X.X
D14
MEL_SAP_PROD
ASET_SAP_APP
melsapprodlrsstor11
SAPMEL-PAPP01
SAPMEL-PAPP02
Production SAP Application Server 02
sapmel-papp02-nic1
X.X.X.X
D14
MEL_SAP_PROD
ASET_SAP_APP
melsapprodlrsstor11
SAPMEL-PAPP03
Production SAP Application Server 03
sapmel-papp03-nic1
X.X.X.X
D14
MEL_SAP_PROD
ASET_SAP_APP
melsapprodlrsstor11
SAPMEL-PLCA01
Production LiveCache Server 01
sapmel-plca01-nic1
X.X.X.X
DS11
MEL_SAP_PROD
ASET_SAP_LCA
melsapprodprmstor13
SAPMEL-PUTL01
Production Utility Server 01
sapmel-putl01-nic1
X.X.X.X
A2
MEL_SAP_PROD
ASET_SAP_UTL
melsapprodlrsstor11
BNW Consulting | SAP Replatform - Detailed Design
24

8.2

Pre-Production

8.2.1 SYD_SAP VM Hostname Description Primary Network Interface IP Address Resource Group Availability Set
8.2.1
SYD_SAP
VM
Hostname
Description
Primary Network Interface
IP Address
Resource Group
Availability Set
Storage Account
Size
SAPSYD-XSQL01
Pre-Prod SQL Node 01
sapsyd-xsql01-nic1
X.X.X.X
D14
SYD_SAP_PREPRD
ASET_SAP_SQL
sydsappprdlrsstor11
Pre-Prod SQL Node 02
sapsyd-xsql51-nic1
X.X.X.X
ASET_SAP_SQL
sydsappprdlrsstor11
SAPSYD-XSQL51
D14
SYD_SAP_PREPRD
SAPSYD-XSCS01
Pre-Prod SX1 SCS Node 01
sapsyd-xscs01-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_SX1_SCS
sydsappprdlrsstor11
SAPSYD-XSCS02
Pre-Prod HRX SCS Node 01
sapsyd-xscs02-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_HRX_SCS
sydsappprdlrsstor11
SAPSYD-XSCS03
Pre-Prod SCX SCS Node 01
sapsyd-xscs03-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_SCX_SCS
sydsappprdlrsstor11
SAPSYD-XSCS04
Pre-Prod POX SCS Node 01
sapsyd-xscs04-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_POX_SCS
sydsappprdlrsstor11
SAPSYD-XSCS05
Pre-Prod BIX SCS Node 01
sapsyd-xscs05-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_BIX_SCS
sydsappprdlrsstor11
Pre-Prod SX1 SCS Node 02
sapsyd-xscs51-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_SX1_SCS
sydsappprdlrsstor11
SAPSYD-XSCS51
SAPSYD-XSCS52
Pre-Prod HRX SCS Node 02
sapsyd-xscs52-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_HRX_SCS
sydsappprdlrsstor11
Pre-Prod SCX SCS Node 02
sapsyd-xscs53-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_SCX_SCS
sydsappprdlrsstor11
SAPSYD-XSCS53
SAPSYD-XSCS54
Pre-Prod POX SCS Node 02
sapsyd-xscs54-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_POX_SCS
sydsappprdlrsstor11
SAPSYD-XSCS55
Pre-Prod BIX SCS Node 02
sapsyd-xscs55-nic1
X.X.X.X
A5
SYD_SAP_PREPRD
ASET_BIX_SCS
sydsappprdlrsstor11
sydsappprdlrsstor11
SAPSYD-XAPP01
Pre-Prod SAP Application Server 01
sapsyd-xapp01-nic1
X.X.X.X
D14
SYD_SAP_PREPRD
ASET_SAP_APP
sydsappprdlrsstor11
SAPSYD-XAPP02
Pre-Prod SAP Application Server 02
sapsyd-xapp02-nic1
X.X.X.X
D14
SYD_SAP_PREPRD
ASET_SAP_APP
Pre-Prod SAP Application Server 03
sapsyd-xapp03-nic1
X.X.X.X
D14
SYD_SAP_PREPRD
ASET_SAP_APP
sydsappprdlrsstor11
SAPSYD-XAPP03
SAPSYD-XLCA01
Pre-Prod LiveCache Server 01
sapsyd-xlca01-nic1
X.X.X.X
DS11
SYD_SAP_PREPRD
ASET_SAP_LCA
sydsappprdprmstor13
SAPSYD-XUTL01
Pre-Prod Utility Server 01
sapsyd-xutl01-nic1
X.X.X.X
A2
SYD_SAP_PREPRD
ASET_SAP_UTL
sydsappprdlrsstor11
BNW Consulting | SAP Replatform - Detailed Design
25

8.2.2

MEL_SAP

VM Hostname Description Primary Network Interface IP Address Resource Group Availability Set Storage Account Size
VM
Hostname
Description
Primary Network Interface
IP Address
Resource Group
Availability Set
Storage Account
Size
SAPMEL-XSQL01
Pre-Prod SQL DR Node 01
sapmel-xsql01-nic1
X.X.X.X
D11
MEL_SAP_PREPRD
ASET_SAP_SQL
melsappprdlrsstor11
Pre-Prod SCS DR Node 01
sapmel-xscs01-nic1
A5
MEL_SAP_PREPRD
ASET_SAP_SCS
melsappprdlrsstor11
SAPMEL-XSCS01
X.X.X.X
SAPMEL-XAPP01
Pre-Prod SAP Application Server 01
sapmel-xapp01-nic1
X.X.X.X
D14
MEL_SAP_PREPRD
ASET_SAP_APP
melsappprdlrsstor11
SAPMEL-XAPP02
Pre-Prod SAP Application Server 02
sapmel-xapp02-nic1
X.X.X.X
D14
MEL_SAP_PREPRD
ASET_SAP_APP
melsappprdlrsstor11
melsappprdlrsstor11
SAPMEL-XAPP03
Pre-Prod SAP Application Server 03
sapmel-xapp03-nic1
X.X.X.X
D14
MEL_SAP_PREPRD
ASET_SAP_APP
SAPMEL-XLCA01
Pre-Prod LiveCache Server 01
sapmel-xlca01-nic1
X.X.X.X
DS11
MEL_SAP_PREPRD
ASET_SAP_LCA
melsappprdprmstor13
SAPMEL-XUTL01
Pre-Prod Utility Server 01
sapmel-xutl01-nic1
X.X.X.X
A2
MEL_SAP_PREPRD
ASET_SAP_UTL
melsappprdlrsstor11
BNW Consulting | SAP Replatform - Detailed Design
26

8.3

QA

8.3.1 SYD_SAP VM Hostname Description Primary Network Interface IP Address Resource Group Availability Set
8.3.1
SYD_SAP
VM
Hostname
Description
Primary Network Interface
IP Address
Resource Group
Availability Set
Storage Account
Size
SAPSYD-QSQL01
QA SQL Node 01
sapsyd-qsql01-nic1
X.X.X.X
D12
SYD_SAP_QA
ASET_SAP_SQL
sydsapqalrsstor11
SAPSYD-QSQL51
QA SQL Node 02
sapsyd-qsql51-nic1
X.X.X.X
D12
SYD_SAP_QA
ASET_SAP_SQL
sydsapqalrsstor11
SAPSYD-QSCS01
QA ST1 SCS Node 01
sapsyd-qscs01-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_ST1_SCS
sydsapqalrsstor11
SAPSYD-QSCS02
QA HRT SCS Node 01
sapsyd-qscs02-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_HRT_SCS
sydsapqalrsstor11
SAPSYD-QSCS03
QA SCT SCS Node 01
sapsyd-qscs03-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_SCT_SCS
sydsapqalrsstor11
SAPSYD-QSCS04
QA POT SCS Node 01
sapsyd-qscs04-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_POT_SCS
sydsapqalrsstor11
SAPSYD-QSCS05
QA BIT SCS Node 01
sapsyd-qscs05-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_BIQ_SCS
sydsapqalrsstor11
QA ST1 SCS Node 02
sapsyd-qscs51-nic1
X.X.X.X
SYD_SAP_QA
ASET_ST1_SCS
sydsapqalrsstor11
SAPSYD-QSCS51
A5
sydsapqalrsstor11
SAPSYD-QSCS52
QA HRT SCS Node 02
sapsyd-qscs52-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_HRT_SCS
sydsapqalrsstor11
SAPSYD-QSCS53
QA SCT SCS Node 02
sapsyd-qscs53-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_SCT_SCS
sydsapqalrsstor11
SAPSYD-QSCS54
QA POT SCS Node 02
sapsyd-qscs54-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_POT_SCS
sydsapqalrsstor11
SAPSYD-QSCS55
QA BIT SCS Node 02
sapsyd-qscs55-nic1
X.X.X.X
A5
SYD_SAP_QA
ASET_BIQ_SCS
SAPSYD-QAPP01
QA SAP Application Server 01
sapsyd-qapp01-nic1
X.X.X.X
D13
SYD_SAP_QA
ASET_SAP_APP
sydsapqalrsstor11
SAPSYD-QAPP02
QA SAP Application Server 02
sapsyd-qapp02-nic1
X.X.X.X
D13
SYD_SAP_QA
ASET_SAP_APP
sydsapqalrsstor11
SAPSYD-QLCA01
QA LiveCache Server 01
sapsyd-qlca01-nic1
X.X.X.X
DS11
SYD_SAP_QA
ASET_SAP_LCA
sydsapqaprmstor13
SAPSYD-QUTL01
QA Utility Server 01
sapsyd-qutl01-nic1
X.X.X.X
A2
SYD_SAP_QA
ASET_SAP_UTL
sydsapqalrsstor11
BNW Consulting | SAP Replatform - Detailed Design
27

8.3.2

MEL_SAP

VM Hostname Description Primary Network Interface IP Address Resource Group Availability Set Storage Account Size
VM
Hostname
Description
Primary Network Interface
IP Address
Resource Group
Availability Set
Storage Account
Size
D11
MEL_SAP_QA
ASET_SAP_SQL
melsapqalrsstor11
SAPMEL-QSQL01
QA SQL DR Node 01
sapmel-qsql01-nic1
X.X.X.X
SAPMEL-QSCS01
QA SCS DR Node 01
sapmel-qscs01-nic1
X.X.X.X
A5
MEL_SAP_QA
ASET_SAP_SCS
melsapqalrsstor11
melsapqalrsstor11
SAPMEL-QAPP01
QA SAP Application Server 01
sapmel-qapp01-nic1
X.X.X.X
D13
MEL_SAP_QA
ASET_SAP_APP
SAPMEL-QAPP02
QA SAP Application Server 02
sapmel-qapp02-nic1
X.X.X.X
D13
MEL_SAP_QA
ASET_SAP_APP
melsapqalrsstor11
SAPMEL-QLCA01
QA LiveCache Server 01
sapmel-qlca01-nic1
X.X.X.X
DS11
MEL_SAP_QA
ASET_SAP_LCA
melsapqaprmstor13
SAPMEL-QUTL01
QA Utility Server 01
sapmel-qutl01-nic1
X.X.X.X
A2
MEL_SAP_QA
ASET_SAP_RTR
melsapqalrsstor11
8.4
Development
VM
Availability
Hostname
Description
Primary Network Interface
IP Address
Resource Group
Storage Account
Size
Set
SAPSYD-DSQL01
Development SQL Server
sapsyd-dsql01-nic1
X.X.X.X
D12
SYD_SAP_NONPROD
ASET_DEV
sydsapdevlrsstor11
SAPSYD-DAPP01
Development SAP Instance Node
sapsyd-dapp01-nic1
X.X.X.X
D12
SYD_SAP_NONPROD
ASET_DEV
sydsapdevlrsstor11
SAPSYD-DLCA01
Development Livecache DB
sapsyd-dlca01-nic1
X.X.X.X
DS11
SYD_SAP_NONPROD
ASET_DEV
sydsapdevlrsstor11
SAPSYD-DUTL01
Development Utility Server 01
sapsyd-dutl01-nic1
X.X.X.X
A2
SYD_SAP_NONPROD
ASET_DEV
sydsapdevlrsstor11
BNW Consulting | SAP Replatform - Detailed Design
28

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.

9 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 SYD iLB Backend Pools LB_SP1_SCS
9.1 Production
Internal Load Balancer
SYD iLB Frontend IP Address
SYD iLB Backend Pools
LB_SP1_SCS
X.X.X.X
X.X.X.X - sapsyd-pscs01-nic1
X.X.X.X - sapsyd-pscs51-nic1
LB_HRP_SCS
X.X.X.X
X.X.X.X - sapsyd-pscs02-nic1
X.X.X.X - sapsyd-pscs52-nic1
LB_SCP_SCS
X.X.X.X
X.X.X.X - sapsyd-pscs03-nic1
X.X.X.X - sapsyd-pscs53-nic1
LB_POP_SCS
X.X.X.X
X.X.X.X - sapsyd-pscs04-nic1
X.X.X.X - sapsyd-pscs54-nic1
LB_BIP_SCS
X.X.X.X
X.X.X.X - sapsyd-pscs05-nic1
X.X.X.X - sapsyd-pscs55-nic1
LB_SMP_SCS
X.X.X.X
X.X.X.X - sapsyd-pscs06-nic1
X.X.X.X - sapsyd-pscs56-nic1
9.2 Pre-Production
Internal Load Balancer
SYD iLB Frontend IP Address
SYD iLB Backend Pools
LB_SX1_SCS
X.X.X.X
X.X.X.X - sapsyd-xscs01-nic1
X.X.X.X - sapsyd-xscs51-nic1
LB_HRX_SCS
X.X.X.X
X.X.X.X - sapsyd-xscs02-nic1
X.X.X.X - sapsyd-xscs52-nic1
LB_SCX_SCS
X.X.X.X
X.X.X.X - sapsyd-xscs03-nic1
X.X.X.X - sapsyd-xscs53-nic1
LB_POX_SCS
X.X.X.X
X.X.X.X - sapsyd-xscs04-nic1
X.X.X.X - sapsyd-xscs54-nic1
LB_BIX_SCS
X.X.X.X
X.X.X.X - sapsyd-xscs05-nic1
X.X.X.X - sapsyd-xscs55-nic1
9.3 Quality

Internal Load Balancer

SYD iLB Frontend IP Address

SYD iLB Backend Pools

LB_ST1_SCS

X.X.X.X

X.X.X.X - sapsyd-qscs01-nic1 X.X.X.X - sapsyd-qscs51-nic1

LB_HRT_SCS

X.X.X.X

X.X.X.X - sapsyd-qscs02-nic1 X.X.X.X - sapsyd-qscs52-nic1

LB_SCT_SCS

X.X.X.X

X.X.X.X - sapsyd-qscs03-nic1 X.X.X.X - sapsyd-qscs53-nic1

LB_POT_SCS

X.X.X.X

X.X.X.X - sapsyd-qscs04-nic1 X.X.X.X - sapsyd-qscs54-nic1

LB_BIQ_SCS

X.X.X.X

X.X.X.X - sapsyd-qscs05-nic1 X.X.X.X - sapsyd-qscs55-nic1

10

Azure Resource Tagging

Following tags will be used, but not limited to:

DEV

QA

PREPROD

PROD

11

OS Backups File Backups SQL Backups
OS Backups
File Backups
SQL Backups

Azure Backup Strategy

Azure backups will adhere to current PACT Azure Backup strategy.

11.1

Use Azure Recovery Services to protect Azure VMs

11.2

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

11.3

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.

Part IX:

SQLSERVER Instance Design

1 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 Release Information 1.1.1 SQLSERVER
http://service.sap.com/instguides -> Database Upgrades -> MS SQL Server
1.1 Release Information
1.1.1 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
User
SQL Server Group
SAPSQLServer_Accounts
1.3 Transparent Data Encryption (TDE)
Current Database are not encrypted, TDE to not be used at PACT

1.4 High Availability

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.

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

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 Instance Trace Settings 1.9.1 SQLSERVER 2014 The following trace flags will be set as
1.9
Instance Trace Settings
1.9.1
SQLSERVER 2014
The following trace flags will be set as per 1986775 – Configuration Parameters for SQL Server 2014
 -T617
Revert a behaviour in SQL Server’s Lock Manager
 -T1117
Proportional File Auto-Growth
 -T1118
Disabling TempDB multi-object extents
 -T2371
Changes to automatic update statistics
 -T2562
Faster CHECKDB runtime
 -T2549
Faster CHECKDB runtime
 -T3226
Suppress successful backup operation log entries
 -T9481
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.

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.

Pool Extension will reside on the local non-persistent disk. TempDBdata<x>.mdf\ndf TempDBlog<x>.ldf 1 .
TempDBdata<x>.mdf\ndf TempDBlog<x>.ldf
TempDBdata<x>.mdf\ndf
TempDBlog<x>.ldf

1.11.1Storage 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.2TempDB 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:

Naming convention for TempDB logfile:

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

Buffer Pool Extension sizing. DB Buffer x 6 BNW Consulting | SAP Replatform - Detailed Design

2

SQLSERVER Cluster Setup

2.1 Hostnames and IP Addresses

2.1.1 Production Cluster Description Nodes Cluster Name Name IP Address SAPSYD-PSQL01 Production SQLServer
2.1.1
Production
Cluster
Description
Nodes
Cluster Name
Name IP
Address
SAPSYD-PSQL01
Production SQLServer
SAPSYD-PSQL51
SAPGEO-PCLU01
X.X.X.X
SAPMEL-PSQL01
2.1.2
Pre-Production
Cluster
Description
Nodes
Cluster Name
Name IP
Address
SAPSYD-XSQL01
Pre-Production SQLServer
SAPSYD-XSQL51
SAPGEO-XCLU01
X.X.X.X
SAPMEL-XSQL01
2.1.3
Quality
Cluster
Description
Nodes
Cluster Name
Name IP
Address
SAPSYD-QSQL01
Quality SQLServer
SAPSYD-QSQL51
SAPGEO-QCLU01
X.X.X.X
SAPMEL-QSQL01

2.2

Cluster Settings

2.2.1 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
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
Fast Failover
Relaxed
Maximum
(Default)
SameSubnetDelay
1
second
1
second
2
seconds
SameSubnetThreshold
5
heartbeats
10
heartbeats
120
heartbeats
CrossSubnetDelay
1
second
2
seconds
4
seconds
CrossSubnetThreshold
5
heartbeats
20
heartbeats
120
heartbeats

3

SQLServer Backup Strategy

Production Backups retained for 1 month Non-Prod Backups retained for 1 month

Landscape Full Diff Tlog Production Weekly Daily 10mins Quality Weekly Daily 1hr Development Weekly Daily
Landscape
Full
Diff
Tlog
Production
Weekly
Daily
10mins
Quality
Weekly
Daily
1hr
Development
Weekly
Daily
30mins

Part X:

SAP System Design

1 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 User SAP Admin account <sapsid>adm SAP
The following user accounts are required for SAP.
Text
User
SAP Admin account
<sapsid>adm
SAP Service account
SAPService<SAPSID>
Users are added to the following AD Group
Text
User
SAP Group
SAP_<SAPSID>_GlobalAdmin

2

SAP Binaries

2.1 SAP Kernel

2.1.1 7.22EXT Kernel

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

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

2.1.2 7.42 Kernel

The following SAP Kernel will be used for all systems based on NW7.4: 7.42 stack
The following SAP Kernel will be used for all systems based on NW7.4:
7.42
stack 300: SAPEXE_300-20012222.SAR & SAPEXEDB_300-20012221.SAR
2.2
SAP IGS
The following SAP IGS will be used:
SAP IGS 7.20_EXT SP10 (igsexe_10-20007794.sar)
SAP IGS HELPER (igshelper_4-10010245.sar)
2.3
SAP CRYPTOLIB
The following SAPCRYPTOLIB will be used:
COMMONCRYPTOLIB 8 patch 8448 (SAPCRYPTOLIBP_8448-20011729.SAR)
2.4
SAP HostAgent
The following SAP HostAgent will be used:
SAP HOST AGENT 7.21 SP11 (SAPHOSTAGENT11_11-20009417.SAR)
2.5
SAP MMC
The following SAP MMC will be used:
SAP MMC 7.42 SP2 (SAP_MMC_2-20012056.MSI)
2.6
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)
SAP JVM 6.1 SP87 (SAPJVM6_87-10006998.SAR)
2.7
SAP WEB DISPATCHER

The following Web Dispatcher version will be used:

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

3

SAP Instance Numbers

3.1 Production Instance Numbers

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

App ASID JSID ASCS AERS JSCS JERS Servers ERP SP1 00 50 00 HR ECC
App
ASID
JSID
ASCS
AERS
JSCS
JERS
Servers
ERP
SP1
00
50
00
HR ECC
HRP
01
51
01
SRM
SCP
02
52
02
EP
POP
13
63
13
BW
BIP
04
54
04
SolMan
SMP
05
55
15
65
05
3.2
Pre-Production Instance Numbers
Pre-Production Instance Numbers will be based on the Production Instance Numbers.
App
ASID
JSID
ASCS
AERS
JSCS
JERS
Servers
ERP
SX1
00
50
00
HR ECC
HRX
01
51
01
SRM
SCX
02
52
02
EP
POX
13
63
13
BW
BIX
04
54
04
3.3
Quality Instance Numbers
Quality Instance Numbers will be based on the Production Instance Numbers.
App
ASID
JSID
ASCS
AERS
JSCS
JERS
Servers
ERP
ST1
00
50
00
HR ECC
HRT
01
51
01
SRM
SCT
02
52
02
EP
POT
13
63
13
BW
BIQ
04
54
04

3.4

Non-Production Instance Numbers

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

3.4.1 Development App ASID JSID ASCS AERS JSCS JERS Servers ERP SD1 00 30 HR
3.4.1
Development
App
ASID
JSID
ASCS
AERS
JSCS
JERS
Servers
ERP
SD1
00
30
HR ECC
HRD
01
31
SRM
SCD
02
32
EP
POD
13
33
BW
BID
04
34
SolMan
SMD
05
15
35

4

SAP Central Services (ASCS & JSCS) Cluster

4.1 SAP SPOF’s (Single Point of Failure) Services

The design of the SAP system is to only have SPOF’s (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)

 JSCS (Java Message Server and Enqueue Server)  Enqueue Replication Server  SAP Gateway
 JSCS (Java Message Server and Enqueue Server)
 Enqueue Replication Server
 SAP Gateway
 WebDispatcher

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 as a Service in the SAP System HA Group. The WebDispatcher will be installed

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

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 Cluster Description Nodes Cluster Name Name IP Address SAPSYD-PSCS01 Production SP1 SAP SCS
4.2.1 Production
Cluster
Description
Nodes
Cluster Name
Name IP
Address
SAPSYD-PSCS01
Production SP1 SAP SCS
SAPGEO-PCLU02
X.X.X.X
SAPSYD-PSCS51
SAPSYD-PSCS02
Production HRP SAP SCS
SAPGEO-PCLU03
X.X.X.X
SAPSYD-PSCS52
SAPSYD-PSCS03
Production SCP SAP SCS
SAPGEO-PCLU04
X.X.X.X
SAPSYD-PSCS53
SAPSYD-PSCS04
Production POP SAP SCS
SAPGEO-PCLU05
X.X.X.X
SAPSYD-PSCS54
SAPSYD-PSCS05
Production BIP SAP SCS
SAPGEO-PCLU06
X.X.X.X
SAPSYD-PSCS55
SAPSYD-PSCS06
Production SMP SAP SCS
SAPGEO-PCLU07
X.X.X.X
SAPSYD-PSCS56
4.2.2 Pre-Production
Cluster
Description
Nodes
Cluster Name
Name IP
Address
SAPSYD-XSCS01
Production SX1 SAP SCS
SAPGEO-XCLU02
X.X.X.X
SAPSYD-XSCS51
SAPSYD-XSCS02
Production HRX SAP SCS
SAPGEO-XCLU03
X.X.X.X
SAPSYD-XSCS52
SAPSYD-XSCS03
Production SCX SAP SCS
SAPGEO-XCLU04
X.X.X.X
SAPSYD-XSCS53
SAPSYD-XSCS04
Production POX SAP SCS
SAPGEO-XCLU05
X.X.X.X
SAPSYD-XSCS54
SAPSYD-XSCS05
Production BIX SAP SCS
SAPGEO-XCLU06
X.X.X.X
SAPSYD-XSCS55
4.2.3 Quality
Cluster
Description
Nodes
Cluster Name
Name IP
Address
SAPSYD-TSCS01
Production ST1 SAP SCS
SAPGEO-TCLU02
X.X.X.X
SAPSYD-TSCS51
SAPSYD-TSCS02
Production HRT SAP SCS
SAPGEO-TCLU03
X.X.X.X
SAPSYD-TSCS52
SAPSYD-TSCS03
Production SCT SAP SCS
SAPGEO-TCLU04
X.X.X.X
SAPSYD-TSCS53
SAPSYD-TSCS04
Production POT SAP SCS
SAPGEO-TCLU05
X.X.X.X
SAPSYD-TSCS54
SAPSYD-TSCS05
Production BIT SAP SCS
SAPGEO-TCLU06
X.X.X.X
SAPSYD-TSCS55

4.3

Cluster Settings

4.3.1 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 Fast Failover Relaxed Maximum (Default) SameSubnetDelay 1 second 1
Windows Server 2012 and later:
Parameter
Fast Failover
Relaxed
Maximum
(Default)
SameSubnetDelay
1
second
1
second
2
seconds
SameSubnetThreshold
5
heartbeats
10
heartbeats
120
heartbeats
CrossSubnetDelay
1
second
2
seconds
4
seconds
CrossSubnetThreshold
5
heartbeats
20
heartbeats
120
heartbeats
4.4 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.

5

SAP System

5.1 Production 5.1.1 SAP Central Services SAP System SCS Virtual Host (Client Access Point) SAP
5.1
Production
5.1.1 SAP Central Services
SAP
System
SCS Virtual Host
(Client Access Point)
SAP User Network
DNS Alias
SP1
SAPGEO-PSP1
X.X.X.X
SAPSP1
BIP
SAPGEO-PHRP
X.X.X.X
SAPHRP
SCP
SAPGEO-PSCP
X.X.X.X
SAPSCP
HRP
SAPGEO-PPOP
X.X.X.X
SAPPOP
POP
SAPGEO-PBIP
X.X.X.X
SAPBIP
SMP
SAPGEO-PSMP
X.X.X.X
SAPSMP
5.1.2 SAP Application Servers
Hostname
Description
SAP User Network
SAPSYD-PAPP01
App Server 1
X.X.X.X
SAPSYD-PAPP02
App Server 2
X.X.X.X
SAPSYD-PAPP03
App Server 3
X.X.X.X
SAPMEL-PAPP01
DR App Server 1
X.X.X.X
SAPMEL-PAPP02
DR App Server 2
X.X.X.X
SAPMEL-PAPP03
DR App Server 3
X.X.X.X
5.1.3 Primary Application Servers
SAP System
Hostname
SP1
SAPSYD-PAPP01
BIP
SAPSYD-PAPP02
SCP
SAPSYD-PAPP03
HRP
SAPSYD-PAPP02
POP
SAPSYD-PAPP01
SMP
SAPSYD-PAPP03
5.1.4 Livecache Servers
SAP System
Hostname
LCP
SAPSYD-PLCA

5.2

Pre-Production

5.2.1 SAP Central Services

SAP System

SCS Virtual Host (Client Access Point)

SAP User Network

DNS Alias

SX1

SAPGEO-PSX1

X.X.X.X

SAPSX1

BIX

SAPGEO-PHRX

X.X.X.X

SAPHRX

SCX

SAPGEO-PSCX

X.X.X.X

SAPSCX

HRX

SAPGEO-PPOX

X.X.X.X

SAPPOX

POX

SAPGEO-PBIX

X.X.X.X

SAPBIX

5.2.2 SAP Application Servers Hostname Description SAP User Network SAPSYD-XAPP01 App Server 1 X.X.X.X
5.2.2 SAP Application Servers
Hostname
Description
SAP User Network
SAPSYD-XAPP01
App Server 1
X.X.X.X
SAPSYD-XAPP02
App Server 2
X.X.X.X
SAPSYD-XAPP03
App Server 3
X.X.X.X
SAPMEL-XAPP01
DR App Server 1
X.X.X.X
SAPMEL-XAPP02
DR App Server 2
X.X.X.X
SAPMEL-XAPP03
DR App Server 3
X.X.X.X
5.2.3 Primary Application Servers
SAP System
Hostname
SX1
SAPSYD-XAPP01
BIX
SAPSYD-XAPP02
SCX
SAPSYD-XAPP03
HRX
SAPSYD-XAPP02
POX
SAPSYD-XAPP01
5.2.4 Livecache Servers
SAP System
Hostname
LCX
SAPSYD-XLCA

5.3

Quality

5.3.1 SAP Central Services

SAP System SCS Virtual Host (Client Access Point) SAP User Network DNS Alias ST1 SAPGEO-PST1
SAP System
SCS Virtual Host
(Client Access Point)
SAP User Network
DNS Alias
ST1
SAPGEO-PST1
X.X.X.X
SAPST1
BIQ
SAPGEO-PHRT
X.X.X.X
SAPHRT
SCT
SAPGEO-PSCT
X.X.X.X
SAPSCT
HRT
SAPGEO-PPOT
X.X.X.X
SAPPOT
POT
SAPGEO-PBIQ
X.X.X.X
SAPBIQ
5.3.2
SAP Application Servers
Hostname
Description
SAP User Network
SAPSYD-TAPP01
App Server 1
X.X.X.X
SAPSYD-TAPP02
App Server 2
X.X.X.X
SAPMEL-TAPP01
DR App Server 1
X.X.X.X
SAPMEL-TAPP02
DR App Server 2
X.X.X.X
5.3.3
Primary Application Servers
SAP System
Hostname
IP Address
ST1
SAPSYD-TAPP01
X.X.X.X
BIQ
SAPSYD-TAPP02
X.X.X.X
SCT
SAPSYD-TAPP01
X.X.X.X
HRT
SAPSYD-TAPP02
X.X.X.X
POT
SAPSYD-TAPP01
X.X.X.X
5.3.4
Livecache Servers
SAP System
Hostname
IP Address
LCT
SAPSYD-TLCA
X.X.X.X

5.4

Development

     

IP

 

SAP System

Description

Hostname

Address

DNS Alias

SD1

SD1 Development

SAPSYD-DAPP1

X.X.X.X

SAPSD1

HRD

HRD Development

SAPSYD-DAPP1

X.X.X.X

SAPHRD

SCD

SCD Development

SAPSYD-DAPP1

X.X.X.X

SAPSCD

POD

POD Development

SAPSYD-DAPP1

X.X.X.X

SAPPOD

BID

BID Development

SAPSYD-DAPP1

X.X.X.X

SAPBID

SMD

SMD Development

SAPSYD-DAPP1

X.X.X.X

SAPSMD

Livecache

Livecache Development

SAPSYD-DLCA1

X.X.X.X

 
Livecache Development SAPSYD-DLCA1 X.X.X.X   BNW Consulting | SAP Replatform - Detailed Design 50

6

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: W Second Letter: SAP System Type using the following values: P – Production
First Letter:
W
Second Letter:
SAP System Type using the following values:
P
– Production
X
– Pre-Production
D
– Development
Q
– QA
C
- Consolidation
T
– Training
S
– Sandpit
Third Letter:
Instance number loosely based on the table in section Production Instance Numbers
6.2 Production WebDispatcher
A WebDispatcher will be installed for each system using the table below.
Message Server
WebDispatcher
WebDispatcher
Instance Nr
SID
Inst_Nr
WebDispatcher
icm http port
00
70 8200
SP1
WP0
01
71 8201
HRP
WP1
02
72 8202
SCP
WP2
13
73 8213
POP
WP3
04
74 8204
BIP
WP4
05
75 8205
SMP
WP5
6.3 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.

7

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. 8 SAP Printing
Synchronisation scripts for Azure files will also run on the utility server.
8
SAP Printing
Print devices are created directly on all app servers.
This is not best practice but is required due to custom code.
9
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.