For effective use of this slide set, we strongly recommend to read through the preface!
•
This slide set is primarily intended as a working tool for the SAP Competence Center; providing support for
our partners and customers.
•
Each of the SAP solutions presented is based on two certified HP ProLiant servers. These proposals are
intended to provide a general reference only; however, these proposals do not replace customer specific
sizing!
•
Mixing the different SAP applications might require different server & storage configurations as proposed in
this guide.
•
This is not a marketing document to position different HP platforms with regard of SAP configurations – it is a
tool for daily sales work.
•
For sizing requests please contact:
Hewlett-Packard GmbH
SAP Competence Center
Altrottstr. 31
D-69190 Walldorf
Germany
• The term CPU is equivalent with socket or processors such as a two CPU Quad Core server contains 8 Cores.
• For availability and performance reasons, HP recommends for SAP ProLiant servers a minimum configuration of two
processors or sockets.
• Depending on customer requirements in relation to data throughput (LAN; SAN); memory extension and scalability of
the server it might be advantageously to choose 4-socket servers as they provide more PCI-slots (data throughput) and
memory slots as 2-socket machines.
• In smaller system landscapes, we offer more powerful server systems than required by SAPS. With Intel Xeon or AMD
Quad Core technology the systems offer huge CPU reserves.
• Although one CPU might be able to cover system requirements of smaller systems (especially for non productive
environments), we recommend using two CPUs.
• For clarification – one 2.0 GHz Quad Core CPU costs about 250€ list price. Also bear in mind that two
CPUs improve server memory addressing and redundancy!
• The sizes of the test- and quality assurance systems are related to the size of the given production system and serve as a
general guide.
• The database sizes are based on SAP CC experiences.
• We strongly recommend to get in touch with our StorageWorks specialists in our SAP CC regarding the following topics:
• Selection of appropriate storage array like SWD All-in-One, storage blades, MSA, EVA or even XP, based on
customer requirements
• Backup & restore and availability concepts considering recovery point, recovery time and general availability
• Consolidation of backup and the various associated topics like tape backup, virtual tape libraries, disk-assisted
backup, local and remote mirroring including cluster integration with CLX or MetroCluster
• Value-added tax (sales tax) is not included in the prices (see separate excel worksheet) listed.
When running business critical processes on an SAP production system, you have to customize
and develop on a separate SAP system, called the development system. Upon completion of
a change, the change needs to be transferred to a
•
quality assurance system (also called test system), where the changes will be tested with
master data, ported from the production system. When it has been verified that the changes
function correctly, these changes will be ported from the development system to the production
system. Consequently, SAP recommends the implementation of at least three systems in every
SAP project.
•
On big systems, we recommend the additional installation of a lab system for testing new
software versions and operational concepts. Another critical task handled by the lab system is to
verify if backups from the production system can be restored, implying that the
database size needs to be the same as that on the production system.
•
If your production system is deployed on a cluster, SAP strongly recommends the
installation of a lab system which is also operated in a cluster.
•
HP recommends to provide high availability for production systems and to use a cluster generally
for 300 users and above.
• The following block diagram is user based. A user based sizing can be done by HP Sizer or SAP
Quicksizer. Quantity based (requires expert know-how) sizing can only be done by SAP
Quicksizer or SAP CC. The description refers to concurrent users; that means SAP users effective
working on the system and not the number of SAP licenses or logged-on users. This is a good
approximation; and this is verified by our experience; is a ratio of one concurrent user for two SAP
licenses (50%).
• As every SAP system has to be customized to the individual customer requirements, it creates
variable load. To provide for adequate system reserves, we estimate a minimum of 10 SAPS (SAP
Application Performance Standard) for each concurrent user that is equivalent to a medium SAP SD
(Sales & Distribution) user.
• The performance of the servers (CPUs) has increased during the last years; you have to put
adequate memory into the servers. A rational starting base for production systems is to calculate 4until up to 8 GB per Core. Be aware that you only get the feasible SAPS values of the respective
servers when using sufficient memory (for instance 32 GB for 2- socket- & 64 GB for 4- socket
servers).
• The size of the database is based on our experience and best practices. On smaller databases we
have to prioritize performance instead of capacity.
The key to improving IT operational effectiveness is to coordinate activities across all the components of your infrastructure.
HP Service includes consistent proactive and reactive services across the whole infrastructure, including hardware, software
and specialized solution support for SAP environments.
Reactive support (Support Plus 24) is delivered through HP’s global support infrastructure. Reactive Support Services
focus on fast and full restoration in the event of a failure, so any problems are fixed quickly and cost-effectively. HP provides
industry-leading call-to-resolution commitments for hardware, including a six-hour call-to-repair commitment for hardware.
HP’s Global Solution Centers are located in key points around the globe, so they can work on any issues 24x7, 365 days a
year.
Proactive onsite support services, delivered by availability and technical experts at your site, help you continually
improve your IT operations. These services are based on industry standards for IT service management, such as ITIL, and HP’s
own experience in managing mission critical business applications. With a proactive approach and remote support
technology HP helps you identify, diagnose and resolve problems before they cause downtime, through monitoring and
analysis of your mission critical environment.
HP Proactive 24 Service helps to improve the stability, availability, and operational effectiveness of your IT environment
through a combination of industryleading technical assistance and proactive account services that cover the entire IT
infrastructure.
HP Critical Service integrates proactive and reactive services to improve availability and performance for businesses where
downtime can be disastrous. Critical Service combines proactive onsite expertise from HP-certified high availability experts,
24x7 priority assistance from HP’s worldwide missioncritical response centers, and proactive remote support tools.
Depending on the size and the complexity of an SAP environment, we propose here a generally adequate service level.
We highly recommend getting in touch with a Service Solution Architect to select and configure the specifically appropriate
service level.
• For Germany, please send service requests to germany.bc@hp.com.
• For EMEA, please send service requests to sap.hp@hp.com
• For AMA, please send service request to pss@hp.com
The information contained herein is subject to change without notice
Onsite Hardware Support
Software Support
Software Updates
Escalationmanagement
HW 4h Call to Repair
SW reactat once
Technology
Solutions
Page 17
SAP BI Sizing Considerations
• The SAP BI configuration examples represent 2 different sizes of BI
landscapes, based on practical experience. The medium configuration
represents the most common type. These examples are intended for a first
budgetary proposal, when no detailed data quantities are available.
• Sizing BI-BPS based on user numbers is not possible!! The 2 examples are
therefore without usage of BI-BPS. For BI-BPS data quantities are
essential!
• A well-founded BI sizing has to be done by defining detailed data quantities
for the SAP Quicksizer tool. To determine the data quantities, the operating
departement and the BI consultant need to collaborate closely.
• Rough data estimations without existing blueprint about BI components
(e.g. number of Info Cubes, ODS Objects ..), cannot lead to a valid sizing
result. Even minor changes in the input parameters can change the result
There is an ABAP Report on the SAP Marketplace available (SAP
Sizing Considerations
Note-917803) that the customer should run over all Info Cubes
that will be transferred into BIA
•
--> please download the latest version of the ABAP Report from the
SAP Marketplace (SAP Note-917803)
•
This means that the customer has to decide in a first step which
Cubes he will shift into BIA. In a second step he should run the
ABAP Report in detail only over these Cubes (that will be shifted
into BIA!!)
• The SAP SRM configuration examples represent 2 different sizes of SRM &
CCM landscapes, based on practical experience. The SRM small
configuration and the CCM medium configuration represent the most
common type.
These examples are intended for a first budgetary proposal, when
no detailed data quantities are available.
• A well-founded SRM sizing has to be done by defining detailed data quantities
for the SAP Quicksizer tool. To determine the data quantities, the operating
department and the SRM consultant need to collaborate closely.
• Rough data estimations without existing blueprint about SRM scenarios
(e.g. self service procurement, plan driven procurement, service
procurement …) to be implemented cannot not lead to a valid sizing result.
Even minor changes in the input parameters can change the result
SAP Solution Manager is a centralized, robust solution management toolset. It empowers companies to implement, operate, monitor,and
support their SAP solutions.
•
SAP Solution Manager facilitates technical support for distributed systems, with functionality that covers all key aspects of solution
deployment, operation, and continuous improvement. It combines tools, content, and direct access to SAP to increase the reliability of
solutions and lower total cost of ownership.
•
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset
addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. As part
of SAP NetWeaver, SAP Solution Manager is included in the annual maintenance fee for SAP solutions.
•
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It
supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your
IT department and your lines of business. And ensures that you derive the maximum benefits from your IT investments.
The previous slides presented server- and storage characteristic information marked
by alphabetic letters for use in the following slides. By combining the specifications
from the T-shirt sizing data with the hardware data, you can build individual system
landscapes and/or size the required components. Configuration and budgeting
(German list price) details can be extracted from a separate Excel worksheet.
• Extra information on the server systems:
• As SAP (especially Java) generally allocates a huge amount of system resources, we
recommend to apply a minimum of 8- optimal 16 GB RAM per server system; as well as
for non-productive systems (behold server sizing categories A & I).
• All systems should be configured with redundant options such as host bus controller; fans
and power supplies (see server configuration layout in the Excel sheet).
• For booting from SAN, you have to plan internal server disks for the page file anyway,
otherwise performance problems will arise.
• Extra information to the storage solutions:
• Listed storage solutions are approved for running SAP; whereas in existing SAP
landscapes the majority is using our Enterprise Virtual Arrays (EVA).
HP Storageworks Enterprise Solution in SAP Environments
EVA 4400, 6100, 8100
EVA is an enterprise class storage array system designed with
a powerfully simple interface
from the storage market leader. Its rich set of software
capabilities keep your data safe even in the most complex of
environments.
Leadership in:
Space
Pooling storage
over very large disk
groups vs.
fractured, small disk
groups; snap copies
into unallocated
space vs. requiring
LUNs to be
reserved.
and the performance you expect
Time
Automated disk
group & LUN set
ups, automated
online LUN
expansions,
automated array
tuning, snap clones
enable our
customers to earn
more revenue
Cost
Enables less
experienced
people to
manage the
array, frees up
higher level
professionals to
create revenue
for the customer,
removes the
opportunities for
human errors.
With EVA, aggregate and automate your array management tasks to manage more
storage capacity with fewer resources.
The following SAP landscape proposals reflect proven solutions that are in widespread
use. A large number of environments with ProLiant server (increasingly blade
environments) and Enterprise Virtual Storage Arrays have been placed in the market
during the last years.
•
Detailed technical and pricing (German list price) information on the following
configuration examples is available (only for HP SAP partners) via a separate Excel
worksheet. As the corresponding infrastructure, such as host bus controllers, FC
switches- and cables, rack and accessory are included and separately illustrated, you
are able to create individual landscapes for budgeting and method of resolution. The
hardware building blocks are separated in rack, server, storage, backup, fibre channel
server- and san components.
• The cluster examples are designed for NetWeaver 2004s. What’s new in 2004s is that
only the critical components of a SAP system are clustered. These are the database and
(A)SCS SAP instance (Message and Enqueue). Additionally SAP application servers are
required to provide dialog, batch, update, spool and gateway services. It is
recommended that the application server is configured as a log on group.
Fibre Channel Storage System
Enterprise Virtual Array 8100 2C6D
• max. 4 disk shelves = 56 disks
• here 84 x 300 GB fc disks 10k/min
• 2 x HSV200-B fibrechannel controller
• fibre to disk technologie
• operating mode up to 4 Gb
• business copy - unlimited
Sizing Considerations:
• Depending on customer requirements and landscape size the applicable servers could be 2; 4 or 8-socket servers; respective the corresponding blade servers as well
• To represent flexibility and for transforming the VMware concept the configuration layout; especially for memory and data throughput might in summary map out
larger than in physical landscapes; especially in the erection phase. SAP CC recommends starting with a minimum of three pyhsical servers.
• Some more factors:
• customer requirements to availability, failover performance & desaster tolerance (such as VMware side recovery manager)
• user behavior
• the choosen SAP applications
• distribution of productive- and non productive systems
To assure a successful course of SAP virtalization projects we highly recommend contacting SAP CC!