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

More documents

Recommendations

Info

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. SCM–OM17 Batch job testing results § 38% performance improvement on the Vblock System 700 compared to the HP-UX platform. © 2013 VCE Company, LLC. All Rights Reserved. 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 manufacturer’s environment. § 50% less hardware was used compared to the customer’s 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. © 2013 VCE Company, LLC. All Rights Reserved. 47
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 and 44: Vblock Systems versus PO8 (active)
Page 45: Test 3: Availability Demonstrate th
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?