Arne Arnold, SAP Field Architect, VMware Sebastian Lenz, Support Engineer, VMware VIRT1138BE #VMworld #VIRT1138BE @vArneArnold @Sebastiano_Lenz #VMworld Unleash the Power of Virtual SAP HANA Deployment VMworld 2017 Content: Not for publication or distribution
31
Embed
VIRT1138BE Unleash the Power of Virtual SAP HANA for … · 2019-06-27 · Arne Arnold, SAP Field Architect, VMware Sebastian Lenz, Support Engineer, VMware VIRT1138BE #VMworld #VIRT1138BE
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Arne Arnold, SAP Field Architect, VMwareSebastian Lenz, Support Engineer, VMware
• VMware Application Workload Guidance provide a comprehensive and extensively tested set of blueprints for building and operating an SDDC.
• This particular whitepaper focuses on virtualized SAP HANA, with SAP HANA Tailored Data Center Integration (TDI) approach, providing information specific to SAP HANA by leveraging existing VMware Validated Design (VVD) for general-purpose guidelines.
VMware Adapter for SAP LaMa integrates SAP Landscape Management (LaMa) with VMware Software-Defined Data Center (SDDC) technologies for automated provisioning and management of a virtualized SAP system.
See more at: http://www.vmware.com/products/adapter-sap-lvm.html
– Optimizations Not Possible in Physical World; Only in the SDDC
• Typical Day 2 Operation Which Can Benefit from NSX
– Enterprise Data Warehouses – data loads from multiple source systems
– Optimization of Scale Out Databases – Identify busy node or nodes
– Backup/Recovery
– Node reconfigurations
– IOT operations, ETL/ELT
– Essentially any data movement within the enterprise
– Latency Sensitive Workloads
17
VMworld 2017 Content: Not fo
r publication or distri
bution
Architecture Guideline and Best PracticeFor running SAP HANA virtualized on VMware vSphere
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP HANA sizing considerations
• The purpose of SAP HANA validation efforts between SAP and VMware is to ensure sizing considerations remains valid. By applying configuration Best Practices performance deviations to bare metal baseline are limited, so sizing can be approached as it would be a usual (non virtualized) environment.
• A usual SAP HANA system sizing starts with (1) the sizing of the SAP application. With the output of this task the SAP HANA HW Partner can then provide (2) a suitable and certified SAP HANA server. Last, (3) the actual VM can be fitted to the needs of the SAP HANA application.
• As virtualization allows for a higher degree of freedom in configuration than SAP HANA HW appliances do, it’s of assents that the vAdmin ensures his VM configuration is made in respect to
“sizing can be approached as it would be a usual (non virtualized) environment.”
#VIRT1138BE CONFIDENTIAL
VMworld 2017 Content: Not fo
r publication or distri
bution
Excurse: Non Uniform Memory Access (NUMA) Fundamentals
21
• Each socket has its own memory controller (IMC).
• While this scales well, memory access is non-uniform:
– local vs. remote access comes with NUMA-effects
• Since SPS 09, SAP HANA targets NUMA-aware thread scheduling & data placement
– Assign memory objects to sockets
– Threads bound to specific socket
– Strategy for data placement to socket & complex query execution plans
RAM
RAM
RAM
Core1 Core2
Core4Core3
CPU 1
Core1 Core2
Core4Core3
CPU 0
Core1 Core2
Core4Core3
CPU 2
Core1 Core2
Core4Core3
CPU 3
RAM
RAM
RAM
RAM
RAM
RAM
RAM
RAM
RAM
high-speed interconnect (QPI)
Local Memory AccessRemote Memory Access
VMworld 2017 Content: Not fo
r publication or distri
bution
Dos and Don’ts for running SAP HANA virtual
CPU resource reservation
•While as vAdmin used to GHz as a metric for CPU consumption, SAP documentation focuses on vCPUs instead. Avoiding over commitment hence refers to the number of committed vCPUs and will be ensured by corresponding CPU resource reservation.
•Unless the host is fully utilized, CPU resource reservations does not have any impact on actual performance.
CPU affinity
•To remain in control of vCPU to physical resource mappings, SAP strongly recommends to use CPU affinity rules to assign vCPUs to cores.
•While affinity rules will vMotion (transfer) with a VM to a different host, such rules may prevent successful startup of a VM e.g. in case of a HA event.
NUMA topology
•Taking NUMA topology into account, wrong virtual to physical mappings may lead to serious performance impacts. The VM CPU configuration (cores per socket) should hence always respect underlying physical topology.
• inhomogeneous environments requires virtual topology to reflect the smaller (older) CPU to still allow e.g. vMotion.
preferHT=on|off
•The use of Intel’s Hyper-Threading technology enables for up to 15% more of SAP HANA performance. That’s why by default HT shall be enabled on host and VM level (See KB article 2003582).
•Note that in this case you need to configure twice the amount of vCPUs than physical cores expressed in SAP sizing.
22
CPU Best Practices
#VIRT1138BE CONFIDENTIAL
VMworld 2017 Content: Not fo
r publication or distri
bution
Dos and Don’ts for running SAP HANA virtual
• In case of SAP, the following parameters shall be set (See SAP Note 1409604):
– on the guest VM level: Tools.GuestLib.EnableHostInfo = true
– on the host level: Misc.GuestLibAllowHostInfo = 1
• It’s further recommended, to configure remote access through SAP router to ease support:
– Connections needs to be maintained on SAP Service Market Place (SMP). Examples of usefully connections related to VMware:
• Connection name: “VMware: vSphere Web Client [instance description]” URL is usually: https://<vCenter Host>:9443/vsphere-client
• Connection name “VMware: vRealize Operations Manager [instance description]”
• If available, VMware recommends using Open VMware Tools (OVT) redistributed by operating system vendors (VMware KB 2073803).
• Ensure that vCPU hotplug is deactivated on hypervisor level, as otherwise vNUMA will get disabled (VMware KB 2040375). Note, that as of today SAP HANA does not support CPU hotplug functionality in general.
• VMware strongly recommends to set sched.cpu.latencySensitivity = normal to avoid negative effects on application level, including disconnects during vMotion actions. (SAP Note 2015392).
• Set Linux kernel parameter elevator = noop to disables I/O scheduling, as ESXi has its own I/O scheduling mechanisms and scheduling I/O inside the Guest OS may cause unnecessary overhead (Red Hat KB 5428 / SUSE KB 7009616)
• Disable Transparent Huge Pages (THP), as THP is not supported for the use with SAP HANA and may lead to hanging situations, as well as performance degradations.
24
Other important config parameters
#VIRT1138BE CONFIDENTIAL
VMworld 2017 Content: Not fo
r publication or distri
bution
OutlookFor running SAP HANA virtualized on VMware vSphere
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP HANA on VMware vSphere Support Roadmap
26
When will my scenario be supported ?
• Will it take as long as last time till support is granted?
• Why does it always take so long?
• May a different platform provide the better options?
VMworld 2017 Content: Not fo
r publication or distri
bution
Virtual SAP HANA Unique Selling Proposition
No T-shirt sizes
•Fill up unused host resources with other VMs
Zero Downtime Hardware Maintenance
•Leverage vMotion for online HW maintenance and replacement
24/7
Homogeneous Landscape Management
•Decouple infrastructure from application management
•Allow OS agnostic monitoring
Built-in takeover capabilities
•Use NSX with SAP HANA System Replication to support automated takeover
•Secure Application and DBMS communication E2E
SAP HANA Try'n'Buy
•Try SAP HANA provisioned by on of VMware's 4000+ vCAN partners
•Migrate VMs online into local DC upon purchase decision
Outlook:vMotion of NVM
•Upcoming NVM technology re-enforces decentralized data storage (on hosts)
•VMware will be uniquely positioned to preserve workload mobility through VMware vMotion
• SAP and VMware will continue their close collaboration to ensure support of future versions for SAP HANA and VMware vSphere, as well as constantly pushing for new scenarios to be added to the list of supported scenarios.
• Goal is to allow even more options and deployment flexibility for VMware virtualized SAP HANA systems.
29#VIRT1138BE CONFIDENTIAL
VMworld 2017 Content: Not fo
r publication or distri
bution
Unleash the Complete Value of SAP | HANA with the SDDC
Agility Availability Lower TCO
Deploy in hours vs. days
Change mgmt.
automation
Self-service for SAP users
99.9%+ availability
Zero downtime migrations
Reduce CapEx by up to 70%
Reduce OpEx by up to 56%
3030
Security
Ensure compliance of security policies
Secure upgrade and patching of SAP
landscapes
99.9%
#VIRT1138BE CONFIDENTIAL
VMworld 2017 Content: Not fo
r publication or distri
bution
@vArneArnold @Sebastiano_Lenz
#VIRT1138BE
VMworld 2017 Content: Not fo
r publication or distri
bution
VMworld 2017 Content: Not fo
r publication or distri
bution
SAP Related Sessions at this year‘s VMworld:
• VIRT1138BEUnleash the power of your virtual SAP HANA deployment
• VIRT1385BEHow Accenture helps their customers to virtualize SAP workloads with VMware solutions to optimize costs and business outcome.
• VIRT2483BESAP on VMware - a customer story: How EVONIK is managing its SAP workload while utilizing market leading SAP and VMware technology
• VIRT2389BESAP on VMware - Customer Group Discussion with EVONIK and SAP on how to run SAP on top of SDDC
• VIRT3014PESAP Virtualization Experts Panel
• MTE4787ESAP in the SDDC including Virtual Hana with Arne Arnold