Using SAP with HP Virtualization and Partitioning

Deployment: Application Perspective
Generally speaking, deployment of SAP systems on virtualization or partitioning technologies based
on the particular application to be used is not recommended. For example, determining that all ERP
applications will be deployed on Virtual Partitions doesn’t take into consideration the users –
developers, testers, or production – or the historical resource utilization of a given ERP system.
Deployment decisions based on what the system is to be used for, as outlined in the previous section,
will typically be more efficient in matching virtualization and partitioning technologies to the SAP
system being deployed. However, there are some exceptions to this heuristic.
Production workloads that do not have stringent response-time characteristics and have a history of
low resource utilization may be good candidates for deployment on shared hardware, i.e., virtual
machines.
Tuning for SAP on HP’s Partitioning Continuum
Configuration and tuning for SAP systems on any of HP’s partitioning or virtualization technologies
should be done just as it would be for a standalone server of the same architecture. If a SAP system
requires a specific OS version, then install that version of the OS in the partition or virtual machine on
which you plan to deploy that SAP system.
In the case of Integrity VM, do not configure the underlying physical system’s OS for the SAP system.
The latter is configured for optimal performance of virtual machines. Apply the SAP system
configuration and sizing to the virtual machine. Specifically, define the VM with the memory,
processors, and storage required for that SAP system. Then install and configure the operating system
and applications on the VM using those same SAP system requirements.
For installation of firmware and software for the partitioning or virtualization technology you plan to
use, consult the release notes for that technology.