HP Smooth Transition Method -

Transcription

1 HP Smooth Transition Method - Customer Stories 2006 Manfred Schlueter Consultant HP/SAP CC, Walldorf 2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

2 Migrations, a painful process SAP Competence Center 2

3 or a smooth transition SAP Competence Center 3

4 Smooth Transition Method Heterogeneous System Copy (Classic R3load) Export Transfer Import FTP, tape,.. anydb Files Files anydb OS HP Smooth Transition Method Read OS OS Write OS CTAS, DBFastTblcopy Oracle Oracle Source Export/Import Destination SAP Competence Center 4

5 Tuning Smooth Transitions Distribute DBFTC Load Tru64 App/DBFTC Tru64 App/DBFTCr Tru64 App/DBFTC DBFTC HP-UX App/DBFTC HP-UX App/DBFTC HP-UX App/DBFTC DB-server DB-server Oracle Export/Import Oracle Source Target SAP Competence Center 5

6 Smooth Transitions: Parallel Execution of Smooth Transitions P01 Oracle... P0n Oracle Oracle Transition Script Generator controlfile controlfile Oracle Transition Script Generator Multiple transitions controlled Job via Execution Plan Scripts UC4 Scheduler Scripts HP-UX Oracle... HP-UX Oracle Multiple SAP Systems Targets SAP Competence Center 6

7 Method Comparison (1) Classic R3LOAD IMIG (Pilot) HPSTM Method type static dynamic & static static Max DB Size (proof point) <= 0.5 (1.7TB) (1) any (2.2 TB) any (6.5TB) Databases any any Oracle None-SAP DB schemas/objects no no yes Explicit Database reorg no no yes Downtime high low low Uptime Low (hours) High (days) Low (hours) Consulting effort medium high low Status GA Pilot GA (all UXes) Certified HP Consultants (2) 60(+20) 1 40 (+40) (1) TB sized databases only with SAP new tools (2) As of Q1/ SAP Competence Center 7

8 Method Comparison(2) Classic R3LOAD IMIG HPSTM Compression of dump yes yes -- (1) Conversion to red. TS layout yes yes no Clean R/3 dictionary yes yes no Change DB SID/schema yes yes yes Migration via LAN No (2) No (2) yes Migration via WAN yes (3) yes (3) No (4) SAP Unicode conversion yes yes no SAP applications any SAP >= 4.0B, no BW, no APO Any, including legacy (5) (1) Dump files can be avoided via parametrization (2) Is possible by using R3load socket option (6.40), not yet for Unicode (3) Due to data compression possible in certain scenarios; workaround: shadow database (4) Will need a minimum 100Mbit WAN throughput; workaround: shadow database (5) Legacy applications on pilot basis SAP Competence Center 8

9 Customer Stories 2004/ SAP Competence Center 9

10 HP STM Reference Customers in all Regions PolyOne, USA Transition of HR (135GB), R/3 (1,6TB) and BW (850GB) Pantja Motors (ATPM), Indonesia Transition of R/3 (2,5TB) to HP-UX/Integrity Burda, Germany Transition of 6 productive SAP systems within one weekend to HP-UX/Integrity SAP Competence Center 10

11 Customer Story end of SAP Competence Center 11

12 Database characteristics impacting performance Type T1 Size Size patterns of tables Size Type T2 Duration Type I1 Size Number of indices Size Type I2 Duration SAP Competence Center 12

13 Migration Results of a POC Runtime [using CTAS, DBFTC, Import/Export, PL/SQL] 1) DB Name Runtime Start Time End Time Throughput rb1 584 GB Perform_Transition Check_Transition Post_Transition 1:35:00 1) 0:00:52 0:23:40 09:30 11:05 11:06 11:05 11:06 11:30 368,8 GB / h rb2 668 GB Perform_Transition Check_Transition Post_Transition 1:47:00 1) 0:00:35 0:23:55 13:50 15:37 15:39 15:37 15:38 16:03 374,5 GB / h rb3 847 GB Perform_Transition Check_Transition Post_Transition 2:50:00 1) 0:00:43 0:30:38 17:15 20:05 20:06 20:05 20:06 20:31 298,9 GB / h 1) Runtimes are based on a Beta-Release of FastTableCopy Test-Migration showed up with a performance increase of approx % SAP Competence Center 13

14 Customer Stories SAP Competence Center 14

15 SAP Server Consolidation Projects Task: replace a complete non HP-based SAP datacenter (73 servers) by HP-UX/Integrity at a large German customer. 62 (+60) SAP systems to be migrated Largest application: 6,5TB SAP BW 3.0B system Project time: 7 months SAP Competence Center 15

16 Migration of a large SAP BW Systems DB size : ca 6,5 TB Database: Oracle Source: IBM ,16 Prozessors@1,9GHz; 262 GB AIX Version 5.2 Target: HP Superdome IA64, 20 Prozessors@1,6 GHz; 152GB, HP-UX SAP Competence Center 16

17 Migration result DB Migration activities Script generation: 2,5 hours => scripts Migration based on HP STM: 21 hours SAP Post-Migration activities: Check und Post migration: 2,5 hours Enduser tests Full offline backup to tape (12 hours) Overall Downtime: 57hours SAP Competence Center 17

18 Customer Story Audi SAP Competence Center 18

19 The Company Audi is one of the leading car manufacturer in Germany Located in Ingolstadt (Bavaria) with factories in Germany and Hungary Part of the Volkswagen group Subsidiaries are: Quattro GmbH (located at Ingolstadt, Germany) Seat (located at Martorell, Spain) Lamborghini (located at Sant Agata Bolognese, Italy) Autogerma (located at Verona, Italy) and some more SAP Competence Center 19

20 The Project The goal is to consolidate Audis SAP system landscape The first step is to consolidate all servers to Ingolstadt This will be combined with a new server platform as the old one runs out of leasing After successful migration of all systems an application consolidation will take place SAP Competence Center 20

21 The RfP In December 2004 Audi asked for the following: a new high available server platform Complete Outsourcing Services (Hosting / Housing) Migration Services Application Management for 45 SAP system landscapes with 107 instances SAP Competence Center 21

22 The Order In May 2005 Audi ordered: Hardware (PA-RISC) Installation Services (OS, MC/SG and SAP) Migration Services for 23 SAP system landscapes with 61 instances (instead of 45/107) Audi did not order: Outsourcing and Application Management Migration of the Interfaces Concepts for network, backup, storage and SAN, SAP Competence Center 22

23 SAP System Overview SAP Versions: R/3 from 4.0b to 4.7 Enterprise Portal 6 BW 3.1 XI 2.0 XI 3.0 SRM 4.0 Learning Solution Solution Manager IDES WAS 6.20 and 6.40 OS Versions: hp-ux 11.0 AIX 4.3.x and 5.x Windows NT Windows 2000 Solaris V9 DB Versions: Oracle 8.0, 8.1 and 9.2 DB2 7.1 on OS/390 MSSQL 8.0 DB Size: from 20 GB to GB SAP Competence Center 23

24 New Platform 10 x HP 9000 rp8420: 100 x dual core CPUs PA x dual core CPUs PA8800 for disaster case (TiCAP) GB RAM SAPS HP-PA was chosen due to SAP XI 2.0 and IBM TSM Both are not supported with Itanium 2 x 22 TB Disk Space (provided by EMC as storage on demand ) Configured as a high available MC/SG cluster using two different data center SAP Competence Center 24

25 Cluster Overview Oracle SAP: ING Systems SAP: EXT Systems SAP1 SAP2 SAP3 Quorum Server ZRZ issap001 issap004 issap005 issap002 issap003 issap000 Bandlager RZN issap006 issap009 issap010 issap007 issap008 CPUs per Server: 10 fixed CPUs 5 TiCAP CPUs 10 fixed CPUs 5 TiCAP CPUs 10 fixed CPUs 5 TiCAP CPUs SAP Competence Center 25

26 Cluster Overview This cluster layout was chosen due to: The Oracle license model Audi forced us to minimize the number of CPUs Oracle can use Maximize flexibility to have the choice to play around with the load of the applications Minimize complexity to have a chance to maintain the environment and to separate the Audi instances from the others Our recommendation: Do not copy this layout! The Oracle cluster may turn out as a bottleneck and it is hard to get rid of this SAP Competence Center 26

27 What happened in the Project There where no predefined standards for the landscape No architectural workshop was scheduled to discuss technical standards. HP had to implement old Audi Standards which where years old and do not fit to an modern SAP environment. The scope changed Continuous during the project from 23 landscapes to 29 and from 61 instances to 72 XI 2.0 went out of scope Audi switched to XI SAP Competence Center 27

28 What happened in the Project The number of SAP system was growing Additional system were installed by Audi so that the overall number grow to 86 instances at the end of the project But in spite of all of this: Only one migration was postponed All migrations happened in time All migrations were successful All migrations were accepted by the customer SAP Competence Center 28

29 Details on the migrations Homogenous migrations from the Ingolstadt Superdome Were done by moving the LUNs around from the old to the new servers Heterogenous migrations from the rest of Europe Step 1)Installation of SAP and Oracle and Integration in MC/SG Step 2)Migration of the Development System Step 3)Test Migration of the Productive System Step 4)Final Migration of the Productive System Step 5)System copy P -> Q Migration of XI Fortunately Audi decided to shut down the XI 2.0 environment and to implement the interfaces on XI 3.0 from scratch as there is no supported migration path from XI 2.0 to SAP Competence Center 29

30 Milestone Plan Year Month System Landscape AHM SRM AHM HR AHM GEMINI SEAT Finanzas SEAT PRENSAS SEAT GEARBOX SEAT RRHH SEAT SPORT Autogerma VAESA Finanzas SID APS AP5 AP6 SEP SPP GEP PRH SSP ANP WFP Sep Oct Nov Dec Jan 2 3 Postponed to April 2006 (Eastern) VAESA HR WRP Systems at Ingolstadt Final Productive Migrations SAP Competence Center 30

31 Data Center consolidation at Audi Transition of AP6 (1) AP6 is a very critical SAP instance This one controls the production of engines for Audi and the accounting of AHM (Audi Hungaria Motor) The Database Size was 800 GB, growing to GB at the end of 2005 and growing further Migration constraints: Transition from Hungary to Ingolstadt Production is running 24 x 6 Annual statement of accounts This has to happen between X-Mas and New Year s Eve So the final migration (including acceptance tests) has been scheduled to Christmas 2005: starting on at 6:00 a.m. ending on at 6:00 a.m SAP Competence Center 31

32 Data Center consolidation at Audi Transition of AP6 (2) Planning the transition of AP6 In the first run it was planned to do the final migration using a shadow database (based on Oracle DataGuard) installed at Ingolstadt to avoid the time needed to physically transfer the export files. This idea was dropped due to technical restrictions with DataGuard and an upgrade of the network bandwidth. Tests using the SAP Migration Monitor showed that it would be possible to do the whole migration within definite less than 72 hours. But due to the objective existing residual risk for the annual statement of accounts Audi cancelled this migration on and postponed it to Eastern SAP Competence Center 32

33 Data Center consolidation at Audi Some Remarks to AP6 (3) Delivering the transition of AP6 Early in March 2006 the window for the final migration was reduced to 48 hours (from Sunday 6:00 a.m. to Tuesday 6:00 a.m.) and we had to look for a faster method than the planned SAP Migration Monitor. The decision was to use the Smooth Transition Method (HP STM) in conjunction with a dedicated temporary WAN line at a speed of 622 MBit/s (instead of 2x 34 MBit/s). This enabled us to do the transition of the 1+TB database over WAN based on HP STM in less than 9 hours. With the additional tasks around (like pre- and postprocessing, system and user tests etc.) the whole migration took 22 hours SAP Competence Center 33

34 Summary SAP Competence Center 34

35 Impact of Infrastructure on HPSTM Performance ES40, 4CPU, 4GB T64 5.1B rx4640, 4CPU, 16GB HP-UX achievable Transfer Speed EMA 1TB rx4640, 4CPU, 16GB HP-UX XP12000 EVA TB rx4640, 4CPU, 16GB HP-UX ~100 GB/h ~200 GB/h GS160, 16CPU T64 HDS rx8620, 16CPU, 64GB HP-UX HDS ~400 GB/h SAP Competence Center 35

36 Database Downtimes in a SAP Environment Downtime in hours R3load 2001 Assumptions: HW scales with database size No pilot Downtime is limited R3load (adv) 2005 IMIG HP STM 2004 HP STM 2005 HP STM Current proposal offerings Pilots DB Size in TB SAP Competence Center 36

37 Migration efforts (per instance) in a SAP Environment Migration efforts High Multiple test runs Complex analysis IMIG R3load (adv) 2005 Assumptions: Maximum a Weekend Downtime HW scales with database size No pilot Medium Complex test runs Special analysis HP STM Low Out of the box usage Max 2 test runs DB Size in TB Disclaimer: A lot of factors will SAP impact Competence migration Center efforts. This graph is just giving a rough guideline. 37

38 Migrating a SAP system is not magic with an experienced migration partner! SAP Competence Center 38

39 SAP Competence Center 39