VIRT1446BU Road to Virtualized HANA on a VMware … · Road to Virtualized HANA on a VMware...
Transcript of VIRT1446BU Road to Virtualized HANA on a VMware … · Road to Virtualized HANA on a VMware...
Mohan Potheri, Vas Mitra
VIRT1446BU
#VMWorld #VIRT1446BU
Road to Virtualized HANA on a VMware Validated Design
VMworld 2017 Content: Not fo
r publication or distri
bution
Agenda
• VMware Validated Design
• Infrastructure Design, SAP Sizing
• High Availability
• Storage , Networking and Security
• Operations
• Workload Validation
2
VMworld 2017 Content: Not fo
r publication or distri
bution
VMware VVD Virtual Infrastructure
• VMware Validated Designs are implemented on a collection of common building blocks, referred to as pods.
• Each pod represents the logical grouping of hardware and software needed to support specific functions within the SDDC.
– Management Pod – It hosts the infrastructure components used to instantiate, manage, and monitor the SDDC
– Shared Edge and Compute Pod – It provides north-south networking access for initial business and end-user workloads. It is typically located inside the same rack as the management pod, although in larger environments it may be installed in a dedicated rack.
4
VMworld 2017 Content: Not fo
r publication or distri
bution
Business Case for Virtualizing SAP S/4 HANA
• Running SAP HANA on vSphere offers customers agility, resource optimization and ease of provisioning.
• This solution enables SAP customers the ability to provision instances of SAP HANA more quickly and effectively by using vSphere virtual machines.
• Using the SAP HANA platform with the VMware vSphere virtualization infrastructure constitutes an optimized environment for achieving a unique, cost-effective solution.
• VMware capabilities such as VMware vSphere vMotion, Distributed Resource Scheduler (DRS), and vSphere High Availability (HA) are innate components of the virtualized SAP HANA platform.
5
VMworld 2017 Content: Not fo
r publication or distri
bution
Application Workload Guidance
• Application Workload Guidance (AWG) provide a comprehensive and extensively-tested set of blueprints for building and operating an SDDC.
• Each design is customized for desired functionality and all applications running in that environment.
• They are holistic and standardized data center-level designs that span across compute, storage, networking, and management, providing a proven framework for how to deploy, configure, and operate an SDDC-based private cloud in support of a wide range of use-cases.
• The documentation included with each AWG includes:
– Solution Overview that details design objectives software components
– Example Design based on customer scenario
6#VIRT1446BU CONFIDENTIAL
VMworld 2017 Content: Not fo
r publication or distri
bution
Example Customer Scenario Requirements
• SAP systems should be sized based on Quick Sizer Output
• Solution should provide appropriate sizing for the customer’s production environment
• Leverage Standard high performance servers for solution
• The project would size for S/4HANA and Suite on HANA based on module availability
• Use SAP HANA TDI Compliant hardware
• Solutions should have end to end monitoring of the infrastructure and the applications
• Solution should provide for security leveraging NSX Micro-segmentation
7
VMworld 2017 Content: Not fo
r publication or distri
bution
Partner Sponsored Physical Infrastructure
• Servers
– Dell R630 for Application Tier
– Dell R730 for DB Tier
• Storage
– TDI certified Pure M50 All Flash Array
– Brocade Generation 6 FC SAN Fabric
– Virtual SAN with Western Digital NVMe and SSD drives
• Networking
– Brocade VDX Switches
9
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP HANA QuickSizer Results – Business Requirements
10
VMworld 2017 Content: Not fo
r publication or distri
bution
QuickSizer Results + Server SAPS Ratings Hosts + VMs
11
ETC….
• SAP Certified benchmarks – server SAPS rating
• If applicable reduce by 10% for virtual
• Assume linear scalability of SAPs with vCPU
• vCPU scheduling and hyperthreading impacts SAPS
SAPS based sizingDetermine hosts + vCPUsAdjust further for memory
Memory based sizing for BW0H
VMworld 2017 Content: Not fo
r publication or distri
bution
NUMA NODE 3, 256 GB
18 Cores, 36 threads
Multi-VM HANA on same host (vSphere 6.x)
1 x ESXi host, 72 cores
NUMA NODE 0 , 256 GB
18 Cores , 36 threads
Core
(2 threads
per core) NUMA NODE 1, 256 GB
18 Cores, 36 threads
NUMA NODE 2, 256 GB
18 Cores, 36 threads
HANA SID 2
VM
HANA SID 1
HANA SID 3 HANA SID 4
When HANA VM needs to be
larger than one NUMA node,
allocate all resource of this
additional NUMA Node
NUMA NODE 3, 256 GB
18 Cores, 36 threads
NUMA NODE 0 , 256 GB
18 Cores , 36 threads
NUMA NODE 1, 256 GB
18 Cores, 36 threads
NUMA NODE 2, 256 GB
18 Cores, 36 threads
vSphere 6.x
vSphere 6.x
https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+HANA+on+VMware+vSphere
VMworld 2017 Content: Not fo
r publication or distri
bution
Hyperthreading Impact on SAPS
13
SAPS throughput
~15% more than
scenario 1
1
2
vCPU
LogicalCPU
Core12 vCPUs on 6 cores
vCPU
LogicalCPU
Core
6 vCPUs on 6 cores
HT benefit ~ 15 % on average
vCPU
LogicalCPU
Core
3
7 vCPUs on 7 cores
SAPS throughput
nearly same as
scenario 2
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP Sizing Tool – Sizing the App Tier
15
5 or 10 way VMs, provides the best VM scheduling/placement for
10 cores per socket
But still ok to go with even number VM sized e.g. 4-way
Target Server: 20 cores per socket
VMworld 2017 Content: Not fo
r publication or distri
bution
HANA “local” HA Solutions
OS
Master
OS
standby
Worker
OS
1
Worker
For SAN: vmdk detach
from failed worker
/attach to standby: this
is managed by Storage
Vendor / 3rd party soln
vmdks
HANAauto host failoverto standby node
HANA
LXOS
primary secondary
Logs (sync mode)2
HANA System
Replication
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP Setup for Validation Tests
HANA
OS
ASCS
OS
app
OS
app
OS
app
OS
HANA
OS
HANA
OS
HANA
OS……
Database level workload validation
SQL Workload
ERP System
Custom ABAP Workload
ERP_HANA3
erphanaapp4(2 vCPU)
Central Services
erphanaapp5 erphanaapp6 erphanaapp7secondary
VMwareFT
1 2
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP Central Services + VMware FT Testing
VMworld 2017 Content: Not fo
r publication or distri
bution
“ping” Test with / without VMware FT
Ping Test FT ON
~1.8ms
ping Test FT OFF
~ 0.3ms
VMworld 2017 Content: Not fo
r publication or distri
bution
Niping Test With / Without VMware FT
Niping Test FT ON
~ 1.5 ms
Niping Test FT OFF
~0.3 ms
“niping” = SAP n/w utility (https://wiki.scn.sap.com/wiki/display/SL/Useful+niping+cmd+for+some+known+network+issue )
VMworld 2017 Content: Not fo
r publication or distri
bution
Custom SAP ABAP Program Creating Locks
• Create lock on table MARA, VBAK, LIKP
• Wait 1 second
• Remove Locks
• Repeat 100 times
• Equivalent to a very fast user opening and closing SAP documents
• Submit program as batch job – use SAP batch txn, “SM37”, to monitor progress
24
VMworld 2017 Content: Not fo
r publication or distri
bution
Enqueue/ Lock Test - SAP Batch Job Results
FT OFF
FT ON
FT
ONFT OFF
Test 1
Test 2Negligible Difference at the
SAP Level
CONCLUSION: Latency due to Central Services + VMware FT measured at the SAP level
by a SAP business user is much different than latency measured at the n/w layer using
n/w utilities
VMworld 2017 Content: Not fo
r publication or distri
bution
Virtual SAN Configuration
• Virtual SAN was used for the Management cluster and as an alternate for the TDI storage for HANA
• All components are vSAN certified from Western Digital (SanDisk)
• Two Disk Groups per server
• Each Disk group contains:
– One NVMe 1.5 TB drive for Caching
– Two 3.5 TB SSD drives for capacity
• Total Capacity of Virtual SAN 52 TB.
28
VMworld 2017 Content: Not fo
r publication or distri
bution
Application Security Leveraging NSX Microsegmentation
30
VMworld 2017 Content: Not fo
r publication or distri
bution
Goal: Configure Micro-Segmentation for SAP ERP
HANA
OS
ASCS
OS
app
OS
app
OS
app
OS
ERP_HANA3
erphanaapp4(2 vCPU)
Central Services
erphanaapp5 erphanaapp6 erphanaapp7secondary
VMwareFT
DB port
enqueue, message, gateway, NFS… etc ports
Need for micro-segmentation in SDDC: East-West traffic shows portion of traffic unprotected by perimeter
firewalls
VMworld 2017 Content: Not fo
r publication or distri
bution
Micro Segmentation – Application Discovery Methods /Tools
32
• Leverage Existing Firewall Policy
• vRealize Network Insight (VRNI)
• NSX Application Rule Manager and Endpoint Monitoring
• vRealize Log Insight
See session “The Road to Micro-Segmentation with VMware NSX [SAI2803BU] “
– Wed Aug 30 3:30-4:30pmVMworld 2017 Content: Not fo
r publication or distri
bution
vRealize Network Insight (VRNI)
33
• Virtual Appliance Model
• Requires Connection to vCenters and Hosts Only
• Analyzes Data Continuously to Generate Traffic Profile and Reports
• Analyze flows between applications or between tiers of an application
• Quickly add VMs to an application tier using vCenterTags or search wildcards
VMworld 2017 Content: Not fo
r publication or distri
bution
VRNI – Define SAP ERP Application
35
4 app tier VMs but discovered 5…extra is secondary VM due to FT
Define App Tier
Define DB Tier
VMworld 2017 Content: Not fo
r publication or distri
bution
VRNI – show flows for SAP ERP
36
Double-click
VMworld 2017 Content: Not fo
r publication or distri
bution
VMware NSX Firewall Rules (screenshot)
38
VMworld 2017 Content: Not fo
r publication or distri
bution
VMware Adapter for SAP Landscape Management
40
See Session “Automatically Deploy, Run, and Manage SAP Applications on VMware’s SDDC Using SAP LaMa and the VMware Adapter for SAP LaMa [VIRT1546BU]”
VMworld 2017 Content: Not fo
r publication or distri
bution
vRealize Operations Dashboards for SAP Operations Management
41
• Nearly every IT component contributes to application performance.
• A lack of visibility can lead to alert storms that drain the productivity of SAP operations.
• Performance issues, particularly across a wide-sprawling application like SAP are hard to track
• Having the ability to clearly see where issues develop can be a game changer
• vROPS Reporting and dashboards can extend the visibility leading to reduction in the duration of outages
• Partner Blue Medora:
• https://bluemedora.com/products/sap/
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP with vRrealize Operations Monitoring Use Cases
42
• See whitepaper “Analyzing SAP Performance with VMware vRealize Operations”
– https://blogs.vmware.com/management/2017/03/analyzing-sap-performance-vrops.html
• Use cases covered:
– Memory capacity planning example based on SAP HANA
• Use VMware Consumed Memory Counter
• Actual HANA memory usage counter available in HANA and extracted by vROPs Management Pack
– Super metric configuration showing Netweaver ABAP memory usage
– SAP on Oracle performance troubleshooting scenario
– Custom dashboard example designed to monitor a SAP database during a heavy data load operation
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP Disaster Recovery with VMWARE Site Recovery Manager
43
VMworld 2017 Content: Not fo
r publication or distri
bution
Testing SAP Workload with and without Hyperthreading
45
0
50
100
150
200
250
300
350
Query 0 Query 1 Query 2 Query 3
Effect of Hyperthreading on SAP Performance
#VIRT1446BU CONFIDENTIAL
HT benefit
VMworld 2017 Content: Not fo
r publication or distri
bution
Performance Validation
• Design was Deployed in Lab
• Validation Tests were performed
• Linear Scalability in performance seen
• Validation of HANA with performance
– OLTP
– DW
– TPC-DS
• HWCCT IO Validation
• Solution was successfully validated for TDI and Virtual SAN storage independently
0
20
40
60
80
100
120
140
160
8 16 32
VDM Queries per second versus vCPU (QPS2)
0
2
4
6
8
10
12
8 16 32
VDM Queries per second versus vCPU (QPS1)
VMworld 2017 Content: Not fo
r publication or distri
bution
vSAN versus TDI Fibre-Channel SAN Storage
• Tests were performed on Pure TDI Storage
• The SAP HANA Virtual Machines were storage vMotioned to vSAN
• The tests were repeated on VSAN
• Here is a comparison of results for two types of queries
• The results show that the performance of the queries are almost identical
47
0
20
40
60
80
100
120
140
160
8 vCPU 16 vCPU 32 vCPU
vSAN versus FC Query Type 2
QPS2 FC QPS2 VSAN
0
2
4
6
8
10
12
14
8 vCPU 16 vCPU 32 vCPU
vSAN versus FC Query Type 1
QPS1 FC QPS1 VSAN
VMworld 2017 Content: Not fo
r publication or distri
bution
Conclusion
• VMWare Infrastructure is the ideal platform for S/4 HANA
• This is the first complete reference architecture depicting the VMware “End-to-End” SDDC solution showcasing the following
– Validated Design and Sizing
– Robust High Availability
– Flexible Software Defined Networking with NSX
– Application Security with Micro-segmentation
– VMware Adapter for SAP Landscape Management
– Solid Operations Management with SAP Dashboards from Blue Medora
– Site Recovery Manager for SAP Disaster Recovery
• Whitepaper available in BCA Home Page: (https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/solutions/vmw-vsphere-virtual-saphana-application-workload-guidance-design.pdf)
49
VMworld 2017 Content: Not fo
r publication or distri
bution