SAP HP ProLiant Master
SAP HP ProLiant Master
SAP HP ProLiant Master
Michael Englert
HP/SAP Competence Center Germany
August 2010
Directory
Subject Slide No.
Preface/Introduction 3–4
Sizing Considerations 5–6
SAP ERP/CRM/SRM 7–8
SAP BW/PI/EP/SCM/Solution Manager 9 – 11
SAP BW Accelerator 12 – 15
HP Services 16 – 17
HP/SAP Scenarios 32 – 36
ERP Cluster scenario with EVA4400 37
ERP Mirrored data center scenario with two EVA6400 38 – 39
Virtualization with P4000 40 – 42
HP BladeSystem Matrix 43 – 45
Further Information 46
• The sizes of the test- and quality assurance systems are related to the size of the current production
system and serve as a general reference.
• 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 Storage Blades, P2000, P4000, 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
• Value-added tax (sales tax) is not included in the prices (see separate excel worksheet) listed.
• 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 base for production systems is to calculate 4 up to 9
GB per 1.000 SAPS. Be aware that you only get the feasible performance values of the respective
servers when using sufficient memory.
• The size of the database is based on our experience and best practices. On smaller databases we
have to prioritize performance instead of capacity.
Concurrent
medium SD 200 User 500 User 1000 User 1500 User > 1500 Users
Users
Solution Management Proactive & Predictive Business Process Monitoring Hot Fix SAP & Non SAP Support
Roadmap Services Process
Implementation Tools Optimization Services System Monitoring Service – Regular Integration SAP Support
Maintenance Activity (OSS)
Analytic engine
InfoCubes
Any source
Data acquisition
= = =
HW Pro Hardware Break HW Pro Reactive Software HW Pro Proactive
Fix Technical Support Deliverables
STS STS SP24 STS P24
• Server prefix
• Complexity/Scalability Levels A, B and C
• Form Factor R (Rack Mount) or B (Blade)
• CPU manufacturer A (AMD) or I (Intel)
e.g. Complex A, Blade Server, AMD CPU ABA is the prefix
• Storage prefix
• Complexity/Scalability Levels A, B, C and D
• Product Line P (P2000/P4000) or E (EVA)
e.g. Complex B, EVA BE is the prefix
• 128 GB Memory
• 256 GB Memory
Contact SAP CC !
• 128 GB Memory
Contact SAP CC !
• 256 GB Memory
Contact SAP CC !
max. user
100 150
(CC recommendation)
Connection Type NAS (iSCSI SAN) SAS
Maximum discs 12 6
Backup / Restore Data Protector (DP) backup solution Data Protector (DP) backup solution
HP P4300 G2 HP P4500 G2
HP P2000 G3
SAS Starter SAN Solution SAS Virtualization SAN Solution
BP-3 up to 300 User
AP-1 up to 150 User BP-1 up to 200 User
Storage characteristic BP-4 up to 500 User
AP-2 up to 600 User BP-2 up to 600 User
BP-5 up to 1000 User
Connection Type FC/iSCSI/SAS dedicated iSCSI SAN
When considering a high available Please plan either the P4300 or the P4500 SAN Solution ; when considering
Overall Sizing Consideration /
Recommendation solution please check with the P4000 or more than 8 storage nodes initially please double-check with the Enterprise
Enterprise Virtual Array offering Virtual Array offering
max. concurrent SAP user for 200 - with initial configuration 200 - with initial configuration 300 - with initial configuration
one SAP system 600 - maximum recommended 800 - maximum recommended 1200 - maximum recommended
(CC recommendation) configuration configuration configuration
Initial configuration 1 Controller Shelf / 12 disk drives 2 Storage nodes / 2 x 8 disk drives 2 Storage nodes / 2 x 12 disk drives
Maximum recommended storage
1 Controller Shelf + 3 disk shelves 8 Storage nodes / 8 x 8 disk drives 8 Storage nodes / 8 x 12 disk drives
nodes/disk shelves
Maximum storage nodes per
- 20 20
P4000 management group
Disk size (SAS exclusively!) 72/146GB (SFF) 300/450GB (LFF) 300/450GB 300/450GB
Sizing rule of Thumb per 100 8 disks at RAID 1+0 plus Network RAID-10 or 12 disks at Raid 5 plus Network
8 disks at RAID 1+0
User RAID-10
Backup / Restore Data Protector (DP) backup solution Data Protector (DP) backup solution Data Protector (DP) backup solution
Storage tools recommendation for • Business Copy (BC) EVA •Business Copy (BC) EVA •Business Copy (BC) EVA
Backup & Restore: • Data Protector (DP) backup solution • Data Protector (DP) backup solution • Data Protector (DP) backup solution
• Tape systems incl. Virtual Tape Library • Tape systems incl. Virtual Tape Library • Tape systems incl. Virtual Tape Library
Disk sizing
• production: ~ 1 TB VRAID 1 net
Fibre channel backup system • test- and qa: ~ 1 TB VRAID 5 net
MSL4048 tape library •development ~ 200 GB VRAID 5 net
• Two Ultrium 1840 drives
• Dataprotector
development system
HP ProLiant DL380 G7
• Server char. A-1
• 2 * Intel Xeon QC 2.13 GHz
• 12 GB RAM
• 2 x 146 GB Raid 1 os, swap
– Application Servers
It is possible to increase the system performance by adding additional application servers
to the configurations. In general it can be assumed that for a standard ECC system the
performance distribution is at least 1:2 (database performance : application
performance). For very database and IO intensive systems it is highly recommended to
use a HP-UX database server. An overall performance of the factor 3 (or more) of the
database server can be achieved. Either a ProLiant Server or a Integrity Server can be
used as an application server.
In this scenario it is assured that if one server node is in maintenance mode there is
still an active 2-node VMware HA Cluster. Therefore it is highly recommended to have
at least 3 server nodes in a virtualized SAP environment
– Sizing
• A hypervisor dependent overhead has to be considered
• No memory over-commitment
• The maximum performance in one single guest system is limited by the maximum configurable
virtual CPUs and memory
– Support
• There are support limitations depending on the hypervisor, Operating System, SAP release, DB
release
Hewlett-Packard GmbH
• SAP Competence Center
• Altrottstraße 31
• D-69190 Walldorf
Germany
Phone: +49 7031 269 302
e-mail: [email protected]
The prodcution server is protected via a spare server concept. This allows to do a failover on the
hardware level with no OS dependency based on the HP VirtualConnect technology.
For the virtualized servers the provided HA solution by the hypervisor can be used as well.
+ + + +
Factory, Tech Virtual Insight Optional Kit:
integration & Connect Software Blades StorageWorks
Financial EVA
Services Virtual Connect
virtualized
Integrity and =
LAN and SAN ProLiant
connections blade servers
Applications
Applications in minutes
Achieve service delivery excellence
Infrastructure
Servers
Servers in minutes
Save > 65% in deployment time
Directory Application Technology Solution
45
45
Further Information
SAP Service Marketplace (S-User required)
SAP Quicksizer (S-User required)
SAP Notes (S-User required)
SAP Community Network
SAP Benchmarks
HP/SAP Alliance
HP Smart Portal (Partner Access required)