SAP OS/DB Migration from HP-UX Platform to Vblock Systems - VCE

More documents

Recommendations

Info

KPI - CPU Performance KPI – Network performance © 2013 VCE Company, LLC. All Rights Reserved. 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 Test 4: Stateless computing Demonstrate stateless computing, in which hardware failure and recovery matches or exceeds the existing system. Demonstrate the provisioning of a UCS blade on the Vblock System 700, using the service profile in case of a blade failure. Number of benchmark users Average dialog response time (sec) Dialog steps per hour SAPS Central server (*) additional specifications Processors Cores Fully processed line items per hour 3,200 0.92 1,055,000 17,580 UCS B200 M1 2 8 351,670 4,852 0.99 1,589,000 26,480 UCS B200 M2 2 12 529,670 Test results summary This section summarizes the results of a proof-of-concept OS/DB migration of SAP from a physical environment running HP-UX to the Vblock System 700 running Red Hat Linux in a virtualized environment. Test results include performance, stress, and batch job processing test results. Performance testing results § Vblock System 700 performed 50% better compared to HP-UX. § Average CPU of HP-UX production was 42.2%. § Average CPU on Vblock Systems was 17%, under the same load. Stress testing results § At 42% CPU usage, HP-UX supported an active user count of 150 and logged-on user count of 1,200. © 2013 VCE Company, LLC. All Rights Reserved. 45
Page 1 and 2: VCE Word Template Table of Contents
Page 3 and 4: Contents Introduction .............
Page 5 and 6: Test 2: Performance ...............
Page 7 and 8: Vblock Systems versus PO8 (quarter
Page 9 and 10: Technology overview This solution u
Page 11 and 12: Environment and configuration detai
Page 13 and 14: Vblock System configuration The fol
Page 15 and 16: Summary comparison of Vblock System
Page 17 and 18: For the SAP DB or application serve
Page 19 and 20: Downloading SAP media Verify that a
Page 21 and 22: Exporting the source system databas
Page 23 and 24: Starting the database export (ABAP+
Page 25 and 26: 8. Provide the Java splitting param
Page 27 and 28: Preparing the target system Perform
Page 29 and 30: 3. Set the parameter mode to Custom
Page 31 and 32: 7. For Installation Method, select
Page 33 and 34: 15. Provide the table space paramet
Page 35 and 36: 2. Provide the software package loc
Page 37 and 38: Fine tuning the database parameters
Page 39 and 40: Solution validation This section de
Page 41 and 42: The following metrics were among th
Page 43: Vblock Systems versus PO8 (active)
Page 47 and 48: Conclusion The traditional method o
Page 49: ABOUT VCE VCE, formed by Cisco and

SAP OS/DB Migration from HP-UX Platform to Vblock Systems - VCE

Create successful ePaper yourself

Delete template?

Save as template?