Table of Contents
www.vce.com
Copyright 2013 VCE Company, LLC. All Rights Reserved. VCE believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." VCE MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OR MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Contents
Introduction ................................................................................................................................. 6
Business case ............................................................................................................................ 6
Key results ................................................................................................................................. 6
Vblock Systems versus PO8 (quarter end) transaction response times ................................ 7
Vblock Systems versus PO8 (active) transaction response times ......................................... 7
Scope ......................................................................................................................................... 7
Objectives .................................................................................................................................. 7
Audience .................................................................................................................................... 8
Feedback ................................................................................................................................... 8
Technology overview .................................................................................................................. 9 Vblock Systems ....................................................................................................................... 9 Vblock System 720 ................................................................................................................. 9 Vblock System 320 ................................................................................................................. 9 SAP components ..................................................................................................................... 10 Environment and configuration details .................................................................................. 11 Customer HP platform and SAP configuration ......................................................................... 11 Database configuration on the HP-UX platform ................................................................... 12 Vblock System configuration.................................................................................................... 13 SAP server configuration on Vblock System 700 ................................................................. 13 SAP database storage configuration on Vblock System 700 ............................................... 14 Summary comparison of Vblock Systems and customers HP configuration .......................... 15 SAP systems sizing considerations ......................................................................................... 16
Migration best practices ........................................................................................................... 18
Preparing the source system ................................................................................................... 18
Downloading SAP media ...................................................................................................... 19
Executing pending updates and deleting canceled updates ................................................ 19
Deleting the QCM tables ...................................................................................................... 19
Deleting all entries from tables TATGPC and TATGPCA ..................................................... 19
Updating R3load, R3ldctl, and R3czchk in the Kernel directory ........................................... 19
Updating the database parameters for sessions and processes .......................................... 19
Increasing the table space for PSAPTEMP .......................................................................... 20
Performing the complete database backup .......................................................................... 20
Running the program SMIGR_CREATE_DDL as a batch job .............................................. 20
Turning off the archive logs and redo logs mirroring ............................................................ 20
Mounting the NFS share with required size for the export dump ......................................... 20
Checking the /tmp file system .............................................................................................. 20
Obtaining root-level access in the source system ................................................................ 20
2013 VCE Company, LLC. All Rights Reserved.
Solution validation .................................................................................................................... 39
Test environment ..................................................................................................................... 39
Test objectives ......................................................................................................................... 39
SAP performance testing ...................................................................................................... 40
Tests ........................................................................................................................................ 41
Test 1: Migration ................................................................................................................... 41
2013 VCE Company, LLC. All Rights Reserved.
Exporting the source system database .................................................................................... 21 Starting the export preparation process in the source system ............................................. 21 Preparing to split tables ........................................................................................................ 21 Starting the database export (ABAP+JAVA) ........................................................................ 23 Preparing the target system ..................................................................................................... 27 Installing all the pre-requisites for SAP on Linux systems .................................................... 27 Installing Java 1.4.2 IBM version .......................................................................................... 27 Adopting OS-level parameters required for Linux systems as recommended by SAP ........ 27 Validating the SAP and Oracle file systems ......................................................................... 27 Enabling the third-party security software to create the system users ................................. 27 Installing the Oracle binaries and performing the database patching................................... 27 Mounting the NFS file system, which contains the export dump .......................................... 28 Creating the migration key .................................................................................................... 28 Adopting the database parameters for the processes and sessions .................................... 28 Importing the database into the target system ......................................................................... 28 Installing SCS and ASCS on the virtual hosts ...................................................................... 28 Importing the database on virtual hosts ................................................................................ 30 Installing the central instance using Java dump ................................................................... 34 Installing the application servers .......................................................................................... 36 Performing post-migration activities ......................................................................................... 36 Fine tuning the database parameters ................................................................................... 37 Starting SAP ......................................................................................................................... 37 Running the installation check .............................................................................................. 37 Installing the license key ....................................................................................................... 37 Reconfiguring Java, performing memory tune-up and testing .............................................. 37 Importing the profiles ............................................................................................................ 37 Start the application servers ................................................................................................. 37 Reconfiguring the STMS and changing the hostnames ....................................................... 37 Changing all the RFC destinations ....................................................................................... 37 Executing the program RS_BW_POST_MIGRATION ......................................................... 38 Performing TEMSE consistency check and cleanup ............................................................ 38 Configuring the logon groups ............................................................................................... 38 Performing a complete backup ............................................................................................. 38
References ................................................................................................................................. 48
Test 2: Performance ............................................................................................................. 42 Test 3: Availability ................................................................................................................. 45 Test 4: Stateless computing ................................................................................................. 45 Test results summary............................................................................................................... 45
Introduction
This document describes best practices for the operating system and database migration of SAP from HP Integrity Superdome servers running PA-RISC/HP-UX to Vblock Systems running x86 Red Hat Enterprise Linux. This paper demonstrates how customers can lower the migration risk of moving from a physical environment running HP-UX to Vblock Systems running Red Hat Linux in a virtualized environment. Traditional infrastructure practices recommend sizing for the worst case, which is an inefficient approach that adds to business risk. With Vblock Systems, customers can plan for the optimum size and take advantage of the dynamic scalability for SAP to support the worst-case scenarios. This paper provides guidance and testing results from a proof of concept (POC) performed for a large semiconductor equipment manufacturing company. The companys SAP landscape includes the following modules: Enterprise Resource Planning (ERP), Supply Chain Management (SCM), Supplier Relationship Management (SRM), Business Intelligence (BI), Process Integration (PI), and Enterprise Portal (EP). The tests involved migration and performance of two core SAP modules, ERP SCM and liveCache. Vblock System 700 was used as the target environment for this migration.
Business case
Virtualization has rapidly gained momentum in enterprise IT environments, because organizations are looking for ways to control escalating hardware costs and to optimize their use of energy and resources while improving business continuity. Virtualization of complex SAP applications can reduce costs and increase speed and resilience. Virtualization also permits faster data analysis and expands data analysis capabilities.
Key results
Key results demonstrate that when deployed on the Vblock System 700, SAP showed performance improvement well over the incumbent hardware. The key findings are: Performance improvement of 50% or more when running SAP on the Vblock System 700 compared with a semiconductor equipment manufacturers environment 50% less hardware used compared to the customers environment Low migration risk moving from an HP-UX based physical environment to a Vblock System 700 virtualized environment Fast recovery of failed application and database server blades with EMC Ionix Unified Infrastructure Manager (UIM) and Cisco Unified Computing System (UCS) service profiles Increased scalability to dynamically add resources High availability and live migration achieved through VMware vMotion
Scope
This document provides best practices for the OS/DB migration of SAP from HP Integrity Superdome servers running PA-RISC/HP-UX to the Vblock System 700 running x86/Red Hat Enterprise Linux.
Objectives
The objectives of this best practices document are to: Show how best practices were used to successfully complete the SAP migration to Vblock System 700 and explain how customers can use the same best practices to perform their migrations. The approaches used for sizing, application layout, storage layout, and the SAP migration procedure were all based on these best practices. Provide the collected testing/monitoring results data associated with the migration. Demonstrate running the applications on the Vblock System 700. Compare performance of Vblock Systems to a customer environment.
Audience
This paper is intended for Vblock Systems customers, SAP administrators and architects, and technical engineering staff, managers, IT planners, administrators, and other IT professionals who are evaluating, acquiring, managing, operating, or deploying SAP in a virtualized data center environment.
Feedback
To suggest documentation changes and provide feedback on this paper, send email to docfeedback@vce.com. Include the name of this paper, the name of the topic to which your comment applies, and your feedback.
Technology overview
This solution uses the following hardware and software components and technologies: Vblock Systems SAP components
Vblock Systems
The Vblock System from VCE is the world's most advanced converged infrastructureone that optimizes infrastructure, lowers costs, secures the environment, simplifies management, speeds deployment, and promotes innovation. The Vblock System is designed as one architecture that spans the entire portfolio, includes best-in-class components, offers a single point of contact from initiation through support, and provides the industry's most robust range of configurations.
SAP components
SAP is one of the key applications in todays data centers, with the largest ERP market share. This test involved migrating the following key SAP components of the customers landscape: ERP Central Component (ECC) 6.0, SCM 5.0, and SAP liveCache. The SAP ERP application is an integrated enterprise resource planning software that targets business software requirements of midsize and large organizations in all industries and sectors. It allows for open communication within and among all company functions. SAP SCM enables collaboration, planning, execution, and coordination of the entire supply chain empowering companies to adapt their supply chain processes to an ever-changing competitive environment. The SAP SCM solution transforms traditional supply chains from linear, sequential steps into an adaptive supply chain network. The SAP liveCache technology significantly increases the speed of the algorithmically complex, dataand runtime-intensive functions of various SAP applications, especially within SAP Supply Chain Management. It combines the advantages of main memory-based data retention with a complete operating concept, including backup and recovery.
10
SAP component ERP Central Component (ECC) 6.0 Supply Chain Management (SCM) 5.0 SAP liveCache 7.6 Customer Relationship Management (CRM) 6.0 Business Information Warehouse (BW) 7.0 Process Integration (PI) 7.0 Supplier Relationship Management (SRM) 5.0 Enterprise Portal (EP) 7.0 Global Trade Services (GTS) 7.1 Governance, Risk, and Compliance (GRC) 5.3 Supply Network Collaboration (SNC) 7.0 Business Objects Enterprise 3.1 Master Data Management (MDM) 7.0 NetWeaver Search and Classification (TREX) 7.0 NetWeaver Composition Environment (CE)
For the OS/DB migration proof of concept, the customers business critical applications SAP ECC, SCM, and liveCache were considered. No other components were migrated.
11
The following table provides details of the servers in the ECC environment on HP-UX.
No. of CPUs 24 24 8 8 8 8 8 Memory (in MB) 147,258 163,641 65,469 65,468 65,468 32,700 65,468
Model ia64 hp server rx8640 ia64 hp server rx8640 ia64 hp server rx8640 ia64 hp server rx8640 ia64 hp server rx8640 ia64 hp server rx8640 ia64 hp server rx8640
Operating system HP-UX 11i v2 (11.23) HP-UX 11i v2 (11.23) HP-UX 11i v2 (11.23) HP-UX 11i v2 (11.23) HP-UX 11i v2 (11.23) HP-UX 11i v2 (11.23) HP-UX 11i v2 (11.23)
The following table provides details of the servers in the SCM environment on HP-UX.
No. of CPUs 8 8 4
Model ia64 hp server rx8640 ia64 hp server rx8640 ia64 hp server rx8640
Operating system HP-UX 11i v2 (11.23) HP-UX 11i v2 (11.23) HP-UX 11i v2 (11.23)
12
Server type Physical Physical Virtual Virtual Virtual Virtual Virtual Virtual
Server ECCPDBCI ECCPDBCI Failover node ECCPDI1 ECCPDI2 ECCPDI3 ECCPDI4 ECCPDI5 ECCPDI6
Hardware UCS B250 M2 UCS B250 M2 UCS B250 M2 UCS B250 M2 UCS B200 M2 UCS B200 M2 UCS B200 M2 UCS B200 M2
OS RHEL 5.5 RHEL 5.5 RHEL 5.5 RHEL 5.5 RHEL 5.5 RHEL 5.5 RHEL 5.5 RHEL 5.5
13
The following table describes the SCM environment on Vblock System 700.
Memory (in GB) 48 48 48 48
vCPU 4 4 4 4
14
15
The following table provides an SAP SCM hardware layout comparison between HP and Vblock Systems.
Server type Database layer Server Server type Configuration OS/DB Number of DB servers SAPS on DB server Server type Application layer Configuration OS Number of App server Total SAPS on App servers Number of App server instances Total SAPS on App server instances HP platform HP Integrity Superdome RX8640 8 cores with 65 GB RAM HPUX 11.23/Oracle 10.2 2 (physical) 14096 (physical) HP Integrity Superdome RX8640 4 cores with 65 GB RAM HPUX 11.23 2 (physical) 7048 (physical) 2 (physical) 7048 (physical) Vblock Systems Virtual machine on UCS B250-M2 4 vCPU with 56 GB RAM RHEL 5.5/Oracle 10.2 2 (virtual) 15970 (virtual) Virtual machine on B200-M2 4 vCPU with 48 GB RAM RHEL 5.5 1 VMware ESXi 15970 (virtual) 2 (virtual) 15970 (virtual)
Based on the current capacity on the HP-UX platform, the same capacity was provided on the Vblock System 700 to provide the same number of SAPS.
16
For the SAP DB or application servers that are running on the virtual platform, SAPS are calculated as follows: Total number of SAPS available on UCS B200-M2/B250-M2: 26,480 Total number of SAPS available for better performance with 65% of CPU and considering 10% VMware overhead: 26,480 x 0.65 x 0.9 = 15,490
# Cisco UCS M2 blade 1 1
No. of CPUs 24 24
Blade # 1 2
SAP server ECCPDBCI ECCPDBCI Failover node ECCPDI1 ECCPDI2 ECCPDI3 ECCPDI4 ECCPDI5 ECCPDI6 SCMPDBCI and liveCache SCMPDBCI Failover node SCMPDI1 SCMPDI2
8 8 8 8 8 8
3 3 4 4 5 5 6
UCS B250 M2 UCS B250 M2 UCS B200 M2 UCS B200 M2 UCS B200 M2 UCS B200 M2 UCS B250 M2
SCMPDBCI
SCMPDI
98,171
7,048
0.45
Virtual
UCS B200 M2
SCMPDI2
4 4
16,316 16,316
3,524 3,524
7 6
0.23 0.23
Virtual Virtual
The following sizing was performed and represents best practices: To use the advantages of the virtualization that is provided on Vblock Systems, all SAP application servers were sized on virtual servers. The ECC database was sized on the physical blade servers based on the customers requirement. The SCM database was sized on the virtualized servers. The liveCache application and its MaxDB database were sized on the virtual servers. Storage sizing was performed using the two-tier sizing method from EMC.
17
For more details on the specific steps, refer to the SAP documentation for heterogeneous system copy, available at www.sdn.sap.com.
19
Mounting the NFS share with required size for the export dump
Separate storage is provided to store the export dump. This storage is mounted as an NFS share on the source system.
20
As soon as the export preparations have completed successfully, the complete export directory with its structure and the generated files that are required for building the target system are transferred to the export dump directory. The dump directory and its subdirectories and files are accessible for <SAPSID>adm of the target system.
21
4.
Set the following general parameters for table splitting: - SAPSID - File with Tables to be split - Export Directory - Number of parallel R3ta run - Database type (Oracle)_
5. 6.
Select the table splitter option. The option for this migration is R3ta table splitter. Type the number of WHR files for each table. The table splitting preparation is successfully completed.
22
23
3. 4. 5. 6.
Provide the SAP profile directory of the source system. Typically, this directory is /sapmnt/SAPSID/profile. Select the method for copying the database content. The Use database specific tools option must be unchecked. Provide the export location for the database export. This location is typically a local directory or an NFS share. Confirm the execution of the report, SMIGR_CREATE_DDL: a. Provide the location for the SQL file directory. You can place the directory in any temporary directory.
b. The option Yes, use the generated SQL files for the system copy must be checked. 7. Set the system parameters for the source system database.
24
8. 9.
Provide the Java splitting parameters. Provide the export parameters. For the Target Hardware Platform parameter, select LittleEndian.
10. Provide the unload options for the database export. Unload Options: -loadprocedure fast. 11. Select the option to run the database statistics updates. In this case, we have chosen to omit the statistics.
2013 VCE Company, LLC. All Rights Reserved.
25
12. Update before the export. 13. After you have finished setting the parameters and options, a summary window opens. Confirm all of your options. Click Next. The export process begins.
26
27
Mounting the NFS file system, which contains the export dump
Mount the NFS file system, which is used in the export process as export dump.
28
3. 4.
Set the parameter mode to Custom. Provide SAP System parameters, such as: a. SAP SID of the target system. b. System mount directory location. Ensure that Unicode System is checked.
5.
Review the prerequisites checker. If there are any severe errors, take the necessary action to resolve them.
29
6. 7. 8. 9.
Click Next. Provide the SCS instance parameter for SCS Instance Number. Typically, this parameter is set to 00. Provide the SCS instance parameter for Internal SCS Message Server Port. Accept the default setting of 3900. Accept the SCS instance number selected in step 7.
10. Provide the software packages and the location. 11. Provide the directory locations where you have stored your installation media. 12. Select the archives that need to be unpacked for the installation. Check all of the checkboxes. 13. After you set the parameters and options, a summary window opens. Confirm all of your options and click Next. The installation process begins. The installation of the SCS instance is successfully completed.
7.
8.
9.
Set the database parameters for the target system database. The database SID should be the same as the SAPSID you selected in earlier steps. Provide the location of the source system database export directory. This is the location where you stored the export from the source system database.
a. c.
Set the password for the database users. Provide the Oracle listener configuration parameter. Typically, this parameter is set to LISTENER_SAPSID;.
31
12. Provide the database instance file systems: ORACLE_HOME, ORACLE_STAGE and sapdata home Directory. 13. Provide the SAP data paths. Ensure that there are a minimum of four SAP data paths. 14. Provide the database specific information shown in the following figure.
32
15. Provide the table space parameters. The following table lists the sizes used in this case.
Table space PSAPSR3 PSAPSR3 PSAPSR3 PSAPSR3700 PSAPSR3701 PSAPSR3DB PSAPSR3USR PSAPUNDO SYSAUX SYSYEM PSAPTEMP PSAPSR3 SAPDATA volume SAPDATA1 SAPDATA2 SAPDATA3 SAPDATA3 SAPDATA3 SAPDATA3 SAPDATA4 SAPDATA3 SAPDATA3 SAPDATA3 SAPDATA4 SAPDATA4 File size (GB) 20 20 20 20 20 20 20 20 10 10 20 20 Number of DB files 46 46 30 6 6 1 9 4 1 1 15 8 Total size (GB) 1000 1000 600 120 120 20 180 80 10 10 300 160
16. Provide the database control file information. Oracle best practices recommend three separate control files. 17. Provide the general load parameters for the database import.
Important: The migration key is intentionally incorrect, in order to pause the import after the database creation. This procedure helps tune the target database and improve the import performance.
18. Select the option to update the database statistics at the end of the import.
33
19. Provide the location of the database media for the installation. After you set the parameters and other options, a summary window opens. Confirm all of your options and click Next. The installation process begins. 20. When the system is ready for the database installation, the SAPinst stops and displays a prompt to start the database installation. Complete the database installation and return to SAPinst.
21. When the database installation is complete, click OK on the SAPinst to resume and complete the installation. The installation is now complete.
34
2. 3. 4. 5. 6. 7. 8. 9.
Provide the software package location you set up in previous steps. Provide the Profile Directory location. Typically, this location is /sapmnt/SAPSID/profile. Type and confirm the SAP Master Password. Set the Oracle Listener Configuration. Type the Central Instance Number. Typically, this number is 01. Accept the default Central Instance parameter values. Provide the location of the software packages. Type and confirm the J2EE Engine Administrator (j2ee_admin) password.
10. Type the Secure Store user (administrator) and password. 11. Select the Interrupt the installation before start of system checkbox. 12. Type the DDIC, client 000 password. 13. Provide the location of the Oracle kernel and Oracle client software packages. 14. Select any desired archives. 15. Provide the SAP Solution Manager Key. Refer the to SAP documentation for information about how to get a solution manager key. 16. Install the Diagnostics Agent.
35
Starting SAP
1. 2. Log on to the target SAP system host. Start the SAP Database and instance.
37
38
Solution validation
This section describes the solution validation and test results.
Test environment
The test environment was set up using HP LoadRunner 9.2.
Test objectives
The test objective is to compare the Vblock System 700 with the HP-UX environment. This test was performed in two major categories: SAP performance testing Operational efficiency of Vblock Systems
Various tests were conducted on an SAP database, central instance, and application server configuration comparable to the large semiconductor companys production configurations. Performance testing was compared to performance test results from the semiconductor companys production P08 and P04 systems. P08 is the SAP Production Planning system. P04 is the SAP (Delta) Materials Management production building block. Testing included these categories: Virtualized SAP application server layer SAP workload balancing using DRS On demand scaling of SAP application servers Online response times tests and batch throughput Stress tests using HP LoadRunner to test Vblock Systems capacity limits Reliability and redundancy of server, storage, and network components Dynamic resource allocation using UIM Migration of various components
39
The following table details the test sets that were performed.
Test Migrate and run SAP ECC, SCM, and liveCache on Vblock Systems Objective Using standard SAP OS/DB migration tools, the VCE team migrates the SAP landscape from the source environment to the Vblock System 700, transporting the data using an external NAS device or network. Deploy SAP Applications ECC and SCM using Adaptive Installation Best Practices. Configure the systems to enable connectivity to a large semiconductor manufacturing companys Adaptive Computing Controller. Apply SAP best practice recommendation for tuning for optimum performance. Demonstrate complete functionality of SAP ECC and SCM systems by logging into the systems and executing a few key basis and sample business transactions. Using standard SAP OS/DB migration tools, the VCE team migrates the SAP landscape from the source environment to the Vblock System 700, transporting the data using an external NAS device or network. The highly available solution for the SAP systems database: SAP CI and DB high availability with Red Hat Linux Cluster suite (Active, Active solution). The highly available solution for the application servers: Multiple DIA and BGD instances on virtual machines distributed on separate ESXi servers. Demonstrate that hardware failure and recovery matches or exceeds existing system. Demonstrate the provisioning of a UCS blade on the Vblock System 700, using the service profile in case of a blade failure.
Demonstrate that SAP performance on Vblock Systems meets or exceeds current benchmarked performance KPIs Demonstrate that the highly available system meets or exceeds the current SLA
The above tests were performed using various tools and techniques. Only Vblock Systems and SAP standard procedures and methods are used to perform benchmarking.
Interactive performance testing For this testing, HP LoadRunner was used to simulate production load (1,200 ECC Dialog Users + Batch Runs + SCM Batch Jobs + Batch Runs) on the SAP Vblock System. The average transaction response times were compared to the service levels provided with the AMAT EWR.
40
The following metrics were among those monitored during the test: Average CPU time Memory Average response time Throughput Average wait time Average load time Database calls Database request
Batch processing To identify capacity limits, batch workload was simulated to significantly increase the workload on the system. In addition to the analysis of the LoadRunner results, usage statistics were gathered at all infrastructure levels (OS, Hypervisor, Storage, and Network) during the runs.
Tests
This section provides details about the tests that were conducted.
Test 1: Migration
Migrate and run SAP ECC, SCM, and liveCache successfully on Vblock Systems.
Test Test 1a Description Using standard SAP OS/DB migration tools, migrate the SAP landscape from the source environment to the Vblock System 700, transporting the data using an external NAS device or network. Deploy SAP Applications ECC and SCM using Adaptive Installation Best Practices. Configure the systems to enable connectivity to a large semiconductor equipment manufacturing companys Adaptive Computing Controller. Apply SAP best practice recommendation for tuning for optimum performance. Demonstrate complete functionality of SAP ECC and SCM systems by logging onto the systems and executing a few key basis and sample business transactions.
Test 1b
Test 1c Test 1d
41
Using best practices, migrate SAP landscape and data to Vblock System 700. Demonstrate improvement running on Vblock Systems.
SAP layer DB OS ECC DB server SAPS on DB server ECC application servers Total SAPS on application servers LoadRunner Customers SAP on HP Oracle HP-UX 11.23 HP Integrity Superdome RX8640 24 cores, 192 GB RAM 21,144 6 X HP Integrity Superdome RX8640 8 cores, 65 GB RAM 42,288 SAPS (physical) N/A SAP on Vblock System 700 Oracle RHEL 5.5 UCS B250-M1 12 cores, 192 GB RAM 26,480 6 x 4 cXPU with 48 GB vRAM (hosted on 3 ESXi servers) 71,496 SAPS (virtual) V9.1
Test 2: Performance
Demonstrate that performance of the SAP system on Vblock Systems meets or exceeds the current benchmarked performance (KPIs). Using standard SAP OS/DB migration tools, the VCE team migrates the SAP landscape from the source environment to the Vblock System 700, transporting the data using an external NAS device or network. Vblock Systems versus PO8 (quarter end) transaction response times The test results showed an overall 55% performance improvement on Vblock Systems.
Transactions VA01 VA02 FAGLB03 MMBE KE30 Vblock Systems (seconds) 0.465 0.315 0.229 2.1 0.953 PO8 (quarter end) (seconds) 1.251 1.298 2.1 1.905 2.28 Percent gain 63 76 89 -10 58
42
Vblock Systems versus PO8 (active) transaction response times The test results showed an overall 62% performance improvement on Vblock Systems.
Transactions VA01 VA02 FAGLB03 MMBE KE30 Vblock Systems (seconds) 0.465 0.315 0.229 2.1 0.953 PO8 (active) (seconds) 1.281 1.358 1.753 2.211 4.417 Percent gain 64 77 87 5 78
43
44
Test 3: Availability
Demonstrate that the highly available system meets or exceeds the current SLA and the availability of the current system.
Test Test 3a Test 3b Description The high availability solution for the SAP systems database: SAP CI and DB high availability with Red Hat Linux Cluster suite (Active, Active solution) The high availability solution for the application servers: Multiple DIA and BGD instances on virtual machines distributed on separate ESXi servers
Processors 2 2
Cores 8 12
Stress testing results At 42% CPU usage, HP-UX supported an active user count of 150 and logged-on user count of 1,200.
45
Highly available system - LR scenario: 1,200 total users, 150 active, production batch load
At 43% CPU usage, the Vblock System 700 supported an active user count of 250 and loggedon user count of 1,800. At 100% CPU usage, the Vblock System 700 supported an active user count of 350 and loggedon user count of approximately 2,500.
SCMOM17 Batch job testing results 38% performance improvement on the Vblock System 700 compared to the HP-UX platform.
46
Conclusion
The traditional method of sizing for SAP landscapes on physical servers is to size for the worst-case demand scenario. This practice is known to have significantly higher initial capital acquisition costs and ongoing operational costs that are decreasing business agility and increasing business risks. This paper alleviates concerns of execution risks and provides guidance to customers who choose to re-platform their SAP landscapes to an x86-based architecture and take advantage of lower capital acquisition costs and virtualization to improve agility. The goals for this POC and the results outlined in this paper were to: Show that best practices were used to successfully complete the SAP migration to the Vblock System 700. Explain how customers can use the same best practices to perform their migration. Provide the collected testing and monitoring results data associated with the migration that also demonstrates running the applications on the Vblock System 700. Compare performance of a Vblock System 700 to a customer environment.
Best practice techniques were used in sizing the application and database servers, storage and filesystem layout. These techniques help remove the guesswork that typically drives such efforts. These best practices involved right-sizing of the Vblock System 700 at compute, storage and network layers. In this POC, it was demonstrated that by using the Vblock System 700: Performance improved 50% or more when running SAP on the Vblock System 700, compared with a semiconductor equipment manufacturers environment. 50% less hardware was used compared to the customers environment. The migration risk was low when moving from an HP-UX based physical environment to a Vblock Systems virtualized environment. Fast recovery of failed application and database server blades was possible with UIM and UCS service profiles. The Vblock System 700 provided increased scalability to dynamically add resources. High availability and live migration were achieved through vMotion.
Next steps
To learn more about this and other solutions, contact a VCE representative or visit www.vce.com.
47
References
Refer to the following sources for supporting and additional information:
Note: To access SAP documentation on the SAP Service Marketplace, SAP requires that you register and have a user ID and password. Contact SAP to set up your user ID.
SAP documentation for heterogeneous system copy www.sdn.sap.com SAP installation guides www.Service.SAP.com
48
ABOUT VCE
VCE, formed by Cisco and EMC with investments from VMware and Intel, accelerates the adoption of converged infrastructure and cloud-based computing models that dramatically reduce the cost of IT while improving time to market for our customers. VCE, through the Vblock Systems, delivers the industry's only fully integrated and fully virtualized cloud infrastructure system. VCE solutions are available through an extensive partner network, and cover horizontal applications, vertical industry offerings, and application development environments, allowing customers to focus on business innovation instead of integrating, validating, and managing IT infrastructure. For more information, go to www.vce.com.
Copyright 2013 VCE Company, LLC. All Rights Reserved. Vblock and the VCE logo are registered trademarks or trademarks of VCE Company, LLC and/or its affiliates in the United States or other countries. All other trademarks used herein are the property of their respective owners.