HP STM SAP System Copy - decus.de · SAPS are release dependent because a SD transaction is always a SD transaction, ... BBP EBP B2B IT-Symposium 2006 17. ... SAP System Copy –

© 2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

SAP System Copy-

SAP‘s StandardMigration Process

2N01 Decus

Manfred SchlueterConsultantHP/SAP CC, Walldorf

21.6.2006 SAP Competence Center 2

Agenda• Driving forces to change the technology stack• SAP Migration methods• Customer examples

IT-Symposium 2006 17. Mai 2006

www.decus.de


Driving Forces to Change• Evolution of SAP applications and technology

• From the integrated SAP R/3 3.1 release to the decoupled, compositeapplications releases in ESA

• From 32 bit to 64 bit applications and technology• System resource requirements can grow by 300+%

• Total Cost of Ownership• End of regular and extended SAP maintenance for all SAP versions <

4.6C in 2006• Ever declining price/performance ratio of standard hardware

components

• Settlement and consolidation of the SAP technology stack: unicode, operating systems, databases, storagecomponents, servers

�


64-Bit platform becomes mandatory for(according to Microsoft SAP Competence Center)

• High User Levels- > 1,000 Concurrent Users (medium -> heavy)

• Unicode- expanding in Eastern Europe / Russia / Asia

• Exchange Infrastructure (XI)• XI is always Unicode

• Business Warehouse / SEM- Large 16-Way Table Joins, >200Gb Data

• SCM / APO- LiveCache (memory resident database)

• Complex Batch Jobs• End of month runs


www.decus.de


Future versions of SAP applicationsexclusively in 64-bit and Unicode after2006

• …New releases of SAP NetWeaver and SAP applications based on SAP NetWeaver, which arereleased in 2007 or later, will no longer supportnew installations of Non-Unicode systems….

• …New SAP product releases as of 2007 will beavailable for 64-bit server operating systems only,including Windows and Linux….

Source: SAP letter to customers, April 2006


TREX 7.1 in next major release of SAP NetWeaverReduction of supported platforms to x86_641. Linux (RedHat & Suse) for x86_642. Windows for x86_64Reason:• Optimize scalability and performance for fewer platforms

more efficiently• Ensure a highly performance-optimized TREX for our

customers• Ensure completeness of 64-bit coding for next release• No negative or limiting impact on other SAP solutions,

because of TREX’internal client/server architecture• Reduce cost of development and support

Source: SAP Sizing Meeting, May 2006


www.decus.de


SAP is Consolidating its Platform Stackthis happened in the past and happens in the future

• Past• Reliant Unix - phased out• VMS - phased out• Alpha/NT - phased out• AS 400 (EBCDIC) - phased out

• Future• Unicode mandatory for ERP 2005, no MDMP support

• Unicode conversion for 10% of all SAP installations• Informix – no Unicode, no WEB AS 7.0• Tru64 Unix – no support for WEB AS 7.0


2011 2012

SAP Release Maintenance Strategy

2002 2003 2004 2005 2006 2007 2008 2009 2010

mySAP ERP

2004

SAP R/3

Enterprise

SAP R/3

4.6C

SAP R/3

3.1I – 4.6B

mySAP ERP

2005

Mainstr.

Maint.

Dec

Dec

Mainstream Maintenance

Extended

Maint.

(17% + 2%)

Dec

Dec

Ramp-

Up

Mar

Dec

Mar

Extended

Maint.

(17% + 2%)

Extended

Maintenance

(17% + 4%)

Extended

Maintenance

(17% + 4%)

Mar

2014

Mar

Mar

Ramp-

Up Mainstream Maintenance



2013

Customer-Specific

Maintenance

Dec

Customer-Specific

Maintenance

Extended

Maint.

(17% + 2%)

Extended

Maintenance

(17% + 4%)

Customer-Specific

Maintenance

Mar

Mar

Extended

Maint.

(17% + 2%)

Extended

Maintenance

(17% + 4%)

Customer-Specific

Maintenance

Extended

Maint.

(17% + 2%)

Extended

Maintenance

(17% + 4%)

Customer-

Specific

Maintenance

Ramp-

Up

today EoS: Oracle Tru64

25%

55%+20%

20%

xx% Est. Percentage of SAP Installations

Alpha

HP-U

X (Itanium)


www.decus.de


System Resource Requirements

R/3 Rel. 3.x 4.0 x 4.5 x 4.6 4.7

CPU 1 +30% +20% +15% +5%

Memory 1 +30% +20% +20%(DB) +5%

+10%(App)

Disk 1 +10% +10% +10% +10%

SAPnote 089305 0113795 0178616 517085

4.7 Unicode

+30% to 35%*

+50%*

+36% to 70%*

Unicode: FAQ*5% if allready double byte

� SAPS are release dependent because a SD transaction is always a SD transaction,

therefore the number of SAPS needed per user is the same from 3.x to 4.7

� The SD transaction in 4.7 is “heavier” than a SD transaction in 3.x – therefore a

Server that has 1000 SAPS with rel 3.x has only 530 with rel 4.7


From R/3 to Enterprise Service ArchitectureDecoupling of process and functionality

mySAP Business

Functionality NetWeaver Integration

Functionality

„mySAP.com“

„new

dimension“

„mySAP“

„Netweaver“

„integration“

„enjoy“

ECC „ ESA“CRM

BI

SRMSSM

ITS

CRMEP

OnlineStore

SFA

BI SRM XIR/3 4.7 SCM

R/3 3.1

R/3 4.0

R/3 4.5

R/3 4.6

APO

SolMgr

CCMS

MDMEEP

SCM

XIMI

BC

Composite Applications

BW

Workplace

BBP

EBP

B2B


www.decus.de


Integrity & Alpha SystemsRelative price and performance, Mar 2005

Alpha Server GS1280Alpha Server GS1280 8/64 EV7, 1.3 GHz 8/64 EV7, 1.3 GHz Alpha Server ES47/80Alpha Server ES47/80 4/8 EV7, 1.15 GHz4/8 EV7, 1.15 GHzAlpha Server ES45Alpha Server ES45 4 EV68, 1.25 GHz4 EV68, 1.25 GHzAlpha Server DS25Alpha Server DS25 2 EV68, 1.0 GHz2 EV68, 1.0 GHzAlpha Server DS15Alpha Server DS15 1 EV68, 1.0 GHz1 EV68, 1.0 GHzIntegrity rx2620Integrity rx2620 2 I2 Madison,1.6 GHz 6M2 I2 Madison,1.6 GHz 6MIntegrity rx4620Integrity rx4620 4 I2 Madison,1.6 GHz 9M4 I2 Madison,1.6 GHz 9MIntegrity rx7620Integrity rx7620 8 I2 Madison,1.6 GHz 6M8 I2 Madison,1.6 GHz 6MIntegrity rx8620Integrity rx8620 16 I2 Madison,1.6 GHz 6M16 I2 Madison,1.6 GHz 6MIntegrityIntegrity SuperDomeSuperDome 8/64 I2 Madison,1.6 GHz 9M8/64 I2 Madison,1.6 GHz 9MWorldwide Reference Price includes 2 GB memory per CPU,

and minimum I/O; no storage or adapters.

10x


Agenda• Driving forces to change the technology stack• SAP Migration methods• Customer examples


www.decus.de


SAP System Copy – Examples

Homogeneous System Copy Heterogeneous System Copy

System Copy

From HP-UX PA-RISC

to HP-UX/Integrity

From IA32 Linux

to Linux/Integrity

From IA32 Windows

to Windows/Integrity

From Alpha/NT

to Windows

No change in database and operating system!

From Tru64 Unix

to HP-UX/Integrity

From Informix

to Oracle

A change in database and/or operating system!


SAP System Copy – SAP Methodologies

Homogeneous System Copy

SAPinst/R3loade.g R/3

- downtime

- effort

SAPinst/IMIGe.g TB-sized DB

- additional load on source

- complexity

DB Export/Importe.g. SAP BW

- downtime

Oracle 10g transportable table spacese.g. R/3 and BW

- not yet supported by SAP- no DB reorganization

HP Smooth Transition Methodall Oracle/SAP apps

+ downtime reduction+ DB reorganization

Heterogeneous System Copy

System Copy

3. Party Tools- not supported by Oracle/SAP


www.decus.de


SAP Migration Requirements• SAP must be informed of intention to migrate• Migration must be done by a certified consultant• Send questionaire & detailed project plan to SAP• Hardware / Database / SAP-Kernel must be

supported• Open an OSS call about the intention to migrate• Sign migration contract with SAP ( contracting

partners are customer & SAP - not! the migrationconsultant )

• Contracts are needed for each PROD-System ( DEV & TEST are for free )


SAP Migration Consultant• is certified techn. consultant ( at least 4.x )• has special certification for migration• no dependency between BC certification and DB /

OS• consultant is on SAP people list to do migrations

Without ?• Support priority is low• Support will be charged• Project maybe reviewed and possible delays


www.decus.de


SAP Migration Team• Migration Consultant• Project Manager internal/external ( depending on project

)• Customers techn. Consultants ( e.g. system admins )• Customers application Consultants ( developers )• „Power Users“ ( functionality check, e.g. FI/CO SD MM )• Customers IT Management


3rd Party Migration Tools• SharePlex from Quest

• Dynamic, complex migration• No support from Oracle and SAP (SAP Note 819826)

• IBM XenoBridge (not yet seen for SAP migrations)

• Oracle TTS & Veritas PDC+ Portable Data Containers (PDC) eliminate the need to move data, just

unmount and mount volumes• Only Oracle 10G supports heterogeneous Transportable TableSpaces

(TTS)• No reorganization of database possible• No support for SAP• Lot of limitations:

• TS has to be self-contained,• source and target have to use the same character set


www.decus.de


SAP Incremental Migration (IMIG)Advantage+ Downtime can be reduced to an acceptable levelDisadvantages– Load on the source systems during IMIG Uptime

� May result in additional resource requirements for the source system– Need for two systems running in parallel (source system and target

system); dynamic migration! High IMIG Uptimes!– SAP recommends to be generous when scheduling an IMIG project to

avoid any problems or escalations due to unforeseen delays. Schedule 6 weeks for each IMIG project.� Expensive consulting projects

- Pilot projects, performed by selected consultants and permission of SAP- Not applicable for SAP SCM, SAP BW, ....- Large variations of downtimes- Difficult proofing, that all BOs got migrated


SAP IMIG Customer Projects

Source: SAP Service Marketplace Q1/2005


www.decus.de


SAP standard migration method• Heterogeneous System Copy (Classic R3load)

anyDB

Source

Files Files anyDB

Destination

Export Transfer Import

FTP, tape, ..

•New SAP Tools•SAP Migration Monitor (parallel exp/imp via net sockets)

•R3TA Table Splitter•SAP Distribution Monitor (in pilot state)


R3load – Advantages• Support by SAP ( exp/imp no more supported )• Database and OS independent• High compression rate of export dump ( rate 1:8 – 1:15 )• Parallel export possible• Restart after failure possible ( only on import )• Checksum of datafile• Database is fully reorganized after import ( e.g. decrease of

extends, tablespace-files, etc. )• Balancing of tablespace files is possible• Splitting option for tuning the export


www.decus.de


R3load – to consider

• No export of nonSAP tables

• Tools differ between releases

• Performance


Customer ExampleMigration from

IBM AIX 4.3.x (8 CPU 800MHz, 12GB RAM, SHARK storage) toHP-UX 11.i (11x875MHz CPU, 24GB RAM)DB (ORACLE) size: 1200GB / 1000GB used

Duration�default method with database optimization: 120h�splitting STR files: 70h�change order of import/export packages: 58h� import parallel to export: 45h�unsorted export: 32h

Never:postpone index creation: you cannot work without indexes!postpone update statistics: you cannot work without statistics!


www.decus.de


Kundenbeispiel

Janz Informationssysteme AG&

Sycor GmbH&HP


„Migrating a SAP system is notmagic with an experiencedmigration partner !“


www.decus.de


© Janz Informationssysteme AG21.6.2006

Janz Informationssysteme AG

Sycor GmbH

Migration einer SAP R/3 Installation

von Tru64 Unix Alpha

nach Windows 2003 Server

auf HP Integrity / EVA

Janz


www.decus.de


Janz

Ausgangssituation:

• SAP R/3 4.7

• 1200 User

• Datenbankgröße 1300 GB

• DB-Server: AlphaServer mit TruCluster

• Applikationserver: 6x 32bit Proliants mit

Linux + 1x Integrity mit HP-UX

• Antwortzeiten ca. 1000 ms, zeitweise

deutlich schlechter

• Weltweiter Druck auf ca. 700 Endgeräte mit

Unispool


Janz

Hardwarelandschaft vor der

Migration

Prod. DB + CIGS806*EV610GB RAM(2000 SAPS)

Test+QA

GS806*EV610GB RAM(2000 SAPS)

6 x SAP ApplikationsServer

SAP Schatten DBAlpha 41002*EV62GB RAM(254 SAPS)

Cluster

log shipping

EMA12000


www.decus.de


Janz

Warum Migration?

• Einfache Datenkopie nicht möglich

• Keine neuen SAP-Releases > 4.7 für Tru64 Unix

• Schlechtes Antwortzeitverhalten

• Inhomogene Landschaft

• 2006: Umstellung auf Unicode und Einführung BW

• Hohe Kosten für

Hardware (Wartung, RZ-Anteil)

Personal (Hoher Schulungsaufwand für einen

Kunden, keine Synergien)


Janz

Vorgaben:

� Gesamtverantwortung liegt beim Lieferanten

� Alles aus einer Hand

� Support des Altsystem

� Drucken zunächst weiter über Altsystem

� Kein Pilotprojekt:

Etabliertes Migrationsverfahren

Referenzinstallationen am Markt

� Downtime maximal 48 Stunden

� Zielplattform: 64-bit Architektur


www.decus.de


Warum Windows?

� Kein ausdrücklicher Kundenwunsch

� Erfüllt alle technischen Voraussetzungen im Zielsegment

� Senkung der Sach-, Personal- und Schulungskosten – KnowHow besser verfügbar

– Windowssupport deutlich günstiger als Unix-Support

– Preisdruck im Outsourcing-Markt

� Reduzierung der zu betreibenden Betriebssysteme imOutsourcing (Verbesserung Servicequalität)

� Zukünftige Wettbewerbsvorteile durch Referenzinstallation


Warum HP Integrity und EVA?

�Itanium: Einzige etablierte 64-Bit Plattform fürWindows 2003

�Flexible Integrity-Server mit Raum für Wachstum

�Fallback auf HP-UX als Option

�EVA: Virtualisierung bringt Performance und Flexibilität

�Gute Integration in bereits vorhandene Management-Instrumente (HP SIM)


www.decus.de


Warum HP?

� schnellstes Migrationsverfahren

� Leistungsvorteile Storage (EVA)

� Altsysteme: Digital/Compaq/HP

– Gute Erfahrungen, Vertrauen in

Systeme/Service

� Professionelle Projektberatung durch HP

und Partner

� HP Strategie mit Integrity/Itanium


Kritische Momente im Projekt

� Enger Zeitplan beim Kunden

� Lieferzeiten Server und Storage

� angewendetes Migrationsverfahren für

Windows nicht erprobt �doch Pilot!

� SAP OSS - Hinweis 2 Tage vor

Produktivmigration � Stopp des Projektes

� „erfolgreiche“ 1. Testmigration


www.decus.de


Ergebnis

� Migration erfolgreich durchgeführt mit einem

Antwortzeitverhalten von ca. 200ms

�In Time und Budget

�professionelle Zusammenarbeit zwischen HP,

Janz und Sycor führte zum Ziel

� Hohe Zufriedenheit beim Endkunden

(es hat auch gar nicht weh getan!)


Dienstleistungsunternehmen im gesamten

Bereich der Informations- und

Kommunikationstechnologie

• 190 Mitarbeiter in Göttingen, Pittsburgh,

Montreal, Shanghai und Singapur

• Fokus: mittelständische Unternehmen in der

produzierenden und verarbeitenden Industrie

• Lösungen und Dienstleistungen rund um:

ERP-Software von SAP und Axapta

Telekommunikation und Netzwerke

Archivierung, E-Business

IT-Outsourcing


www.decus.de


•

Janz


www.decus.de

Documents

HP STM SAP System Copy - decus.de · SAPS are release dependent because a SD transaction is always a SD transaction, ... BBP EBP B2B IT-Symposium 2006 17. ... SAP System Copy –