HP Smooth Transition Method 2N02 Decus · SAP System Copy – SAP Methodologies Homogeneous System Copy SAPinst/R3load e.g R/3 - downtime - effort SAPinst/IMIG e.g TB-sized DB - additional

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

HP Smooth TransitionMethod

-2N02 Decus

Manfred SchlueterConsultantHP/SAP CC, Walldorf

21.6.2006 SAP Competence Center 2

Agenda• Smooth Transitions for SAP Customers

• SAP Migration methods• HP „Smooth Transition“ method (HPSTM)

• HP STM project experiences• Tru64/SAP Transition process and HP deliverables

IT-Symposium 2006 17. Mai 2006

www.decus.de


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


Migrations, a painful process ...


www.decus.de


Customer‘s Pain Points withSAP Migrations

•Major business disruptions•Migrating a 2.5 TB sized database will need 4-5 days ofproduction downtime/restrictions in a manufacturing plant•Migrating a complete SAP landscape (multipleapplications) has to be spread over a couple of weekends•If the migration threatens to fail, what is the fall-backsolution? How much time is needed to revive the businessapplications?

•Investment protection•Hardware & Software,•Skills and Knowledge•Migration costs


…or a smooth transition


www.decus.de


Smooth Transition Method• Heterogeneous System Copy (Classic R3load)

anyDB

OS

Files FilesanyDB

OS

Export Transfer Import

FTP, tape, ..

• HP Smooth Transition Method

Oracle

Source

Oracle

Destination

CTAS, DBFastTblcopy

Export/Import

OS OSRead Write


Application Migration DowntimeWindow• Customer defines Downtime Window:

• Time, where the application is not available forproductive use.

• In case of a not successful migration, the old landscapehas to be available within the limits of the downtimewindow

• Downtime relevant migration activities• Pre-migration tasks• Database migration• Post-migration tasks

• SAP reports (e.g sgen, RFC destinations, …)• Power user functional tests• Backup of database• Cut-over decision


www.decus.de


Database Downtimes in a SAP Environment

1 2 3 4 5 6

Downtimein hours

10

20

30

40

50

60

70

80

90

DB Sizein TB

HP STM 2004

R3load 2001

HP STM 2006

HP STM 2005

R3load (adv) 2005

Current proposal offeringsPilots

Assumptions:•HW scales with database size•No pilot•Downtime is limited

IMIG


Migration efforts (per instance) in a SAP Environment

1 2 3 4 5 6

Migration efforts

Low•Out of the box usage•Max 2 test runs

Medium•Complex test runs•Special analysis

High•Multiple test runs•Complex analysis

DB Sizein TB

HP STM

R3load (adv) 2005

IMIG

Assumptions:•Maximum a Weekend Downtime•HW scales with database size•No pilot

Disclaimer: A lot of factors will impact migration efforts. This graph is just giving a rough guideline.


www.decus.de


Method Comparison (1)

yesnonoNone-SAP DB schemas/Objects

staticdynamic & staticstaticMethod type

GA (all UXes)PilotGAStatus

yesnonoExplicit Database reorg

40 (+40)160(+20)Certified HP Consultants(2)

lowhighmediumConsulting effort

Low (hours)High (days)Low (hours)Uptime

lowlowhighDowntime

OracleanyanyDatabases

any (6.5TB)any (2.2 TB)<= 0.5 (1.7TB)(1)Max DB Size (proof point)

HPSTMIMIG (Pilot)ClassicR3LOAD

(1) TB sized databases only with SAP new tools(2) As of Q1/2006


Method Comparison(2)

--(1)yesyesCompression of dump

yesNo(2)No(2)Migration via LAN

Any, includinglegacy(5)

>= 4.0B, no BW, no APO

any SAPSAP applications

noyesyesSAP Unicode conversion

No(4)yes(3)yes(3)Migration via WAN

yesyesyesChange DB SID/schema

noyesyesClean R/3 dictionary

noyesyesConversion to red. TS layout

HPSTMIMIGClassicR3LOAD

(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


www.decus.de


Method Comparison (3)

staticdynamicMethod type

NANAStatus

no(no)Database reorg

??HP Consultants

mediumVery highConsulting effort

Low (hours)High (days)Uptime

Very lowVery lowDowntime

nonoUnicode conversion

Oracle 10GOracleDatabases

nonenoneSAP apps

anyanyMax DB Size

Data MirrorVeritas PDC&TTSShareplex


Typical HPSTM Transition Process

Source Target

Tru64 Unix 5.1B HP-UX 11i V2

GbE

Oracle

OracleTransitionScriptGenerator

1Controlmodule

OracleTransitionScripts

2

Oracle 9.2 3

CTAS, DBFastTblCopy

Export/Import;

>90% of data

<10%

4


www.decus.de


HP STM Platforms supported

HP platforms onlyany serverServer

HP-UX, Linux4,Windows4, Tru64

any SAP certifiedOS

OS

>= Oracle 9.2.0.62>=Oracle 8.1.7Database

any SAPany SAP1Application

Target3Source3

1 any legacy application on an individual project basis2 Oracle upgrade and Oracle reorg included3 supported according to service.sap.com/PAM4 no native support of DBFTC for these OS.


HP Smooth Transition MethodCharacteristics�Reducing downtime by a factor of 5 - 10

�Throughput from 100GB/h up to 374GB/h�Time measured from stop of SAP until the first SAP GUI

appears on new platform

�Reducing consulting effort�Reducing complexity�Support via HP, Oracle�DB Reorganisation inclusive�Risc mitigation�Migration costs reduction


www.decus.de


HP Smooth Transition MethodUnique Advantage Points

• Massive reductions of downtime &consulting efforts

• Flexibility – customizable toolset (migrations,reorganizations, database copy)

• State-of-the-Art Oracle target database setup(including LMTS, ASSM)

• High degree of automation & resilience






www.decus.de


Migration Results of a POCRuntime [using CTAS, DBFTC, Import/Export, PL/SQL] 1)

298,9 GB / h

20:05

20:06

20:31

17:15

20:05

20:06

2:50:00 1)

0:00:43

0:30:38

Perform_Transition

Check_Transition

Post_Transition

rb3847 GB

374,5 GB / h15:37

15:38

16:03

13:50

15:37

15:39

1:47:00 1)

0:00:35

0:23:55

Perform_Transition

Check_Transition

Post_Transition

rb2668 GB

11:05

11:06

11:30

End Time

368,8 GB / h

09:30

11:05

11:06

1:35:00 1)

0:00:52

0:23:40

Perform_Transition

Check_Transition

Post_Transition

rb1584 GB

ThroughputStart TimeRuntimeNameDB

1) Runtimes are based on a Beta-Release of FastTableCopy

Test-Migration showed up with a performance increase of approx. 40-50 %


Impact of Infrastructure on HPSTM Performance

ES40, 4CPU, 4GB

T64 5.1B

EMA1TB

rx4640, 4CPU, 16GBHP-UX

EVA 30001TB

~100 GB/h



XP12000~200 GB/h

GS160, 16CPUT64

HDS


HDS~400 GB/h

achievable Transfer Speed


www.decus.de


Database characteristics impactingperformance

Size Size

Duration

Duration

Size Size

Size patterns of tables

Number of indices

Type T1

Type I1

Type T2

Type I2


Tuning Smooth Transitions (1)Distribute DBFTC Load

Oracle

Source

Oracle

Target

Export/Import

DB-server

Tru64App/DBFTC

Tru64App/DBFTCr

Tru64App/DBFTC

HP-UXApp/DBFTC

HP-UXApp/DBFTC

HP-UXApp/DBFTCDBFTC

DB-server


www.decus.de


Tuning Smooth Transitions (2)

Oracle

Multiple, synchronised Sources

Oracle

Target

CTAS, DBFastTblcopy

Export/Import

P

HP-UX

Oracle

Stdby

HP-UXHP-UX

Input from multiple Sources, Output to multiple destinations


More in Less Time:Parallel Execution of Smooth Transitions

Oracle

Multiple SAP Systems

Oracle

Targets

P01 HP-UX

Oracle

P0n

Oracle

HP-UX

....



Scripts

Scripts

....


www.decus.de


Smooth Transitions:Parallel Execution of Smooth Transitions

Oracle

Multiple SAP Systems

Oracle

Targets

P01 HP-UX

Oracle

P0n

Oracle

HP-UX

....

Multipletransitionscontrolled

via

UC4Scheduler



controlfile

controlfile JobExecutionPlan

Scripts

Scripts

....


Smooth Transitions:Pre & Post Migration Tasks

Oracle

Source

Oracle

Target

Tru64 HP-UXMultiple

tasks controlledvia

UC4Scheduler

Pre-migrationtasks

Migrationtasks

Post-migrationtasks


www.decus.de


Transition Investment Advantages

$Delta Training

$$Storage Foundation

$$$Mixed Environment

$$$$$$$$$$$$$$Total

$$$$HPSTM Service

$$Cluster

$OS

$$$$Hardware

...other...HP-UXTransition from Tru64 Unix to ...






www.decus.de


SAP Heterogeneous MigrationProcess ...

... is defined by SAP and we follow the overallprocess step-by-step.

Instead of applying R3INST/R3LOAD we useHPSTM.


HP Transition Services• Integrated transition proccess

• Transition Consulting Workshop (HP)• SAP OS/DB Migration Checks (SAP)• Smooth transition services (Oracle & HP)

• Today > 120 SAP base consultants at HP whocould deliver migration services (SAP certified)

• ~60 HP&Oracle SAP migrations consultants trainedon HP STM


www.decus.de


Plan Transition

Target BOM

Migration Schedule

Assess source apps

Configure & install target

Target OS

Target Storage

Network

Install SAP apps

DC integration

test migration pre-tasks

Order keys and

Licenses;

Run HPSTM or R3load/SAPinst

Install tools; Create

database; Execute

and control transition

tasks

test migration post-tasks

Run SAP reports;

Verify & Test SAP application

productivemigration pre-tasks

Run HPSTM or R3load/SAPinst

Transition Consulting Workshop

Planning a transition;

Transition

deliverables; Tru64 /

HP-UX differences

productivemigrationpost-tasks

Transition Assessment WS

Scoping the project;

# SAP systems affected

Customer requirements

Consolidation

Resizing & Design

Mapping of Apps to

infrastructure

Definition of

transition environment

Verify & Test SAP productiveapplication

GoLive

SAP migration app1

SAP migration appn

Minimum once

Exactly once

Production

Support


MAEMADAS

Source

T64

SAP<4.6c

SAP/T64 Customer Upgrade /Transition Options

EVAXPHP-UX

IA64

SAP4.6c/4.7

Not possible

HP-UXPA-Risc

SAP<4.6c

Transition to HP-UX/PA-Riscvia HPSTM

Upgrade &

Homogeneous

Copy

Target

MAEMADAST64

SAP4.6c/4.7

Transition

Upgrade

In 2006: Upgrade&

Transition&

Unicode Conversion

MAEMADAST64

ERP2005

Transition to HP-UX/Integrityvia HPSTM

EVAXPHP-UX

IA64

ERP2005

Upgrade & UnicodeConversion

Upgrade


www.decus.de


MAEMADAS

Source

T64

SAP<4.6c

SAP/T64 Customer Upgrade /Transition Options

EVAXPHP-UX

IA64

SAP4.6c/4.7

Not possible

HP-UXPA-Risc

SAP<4.6c

Transition to HP-UX/PA-Riscvia HPSTM

Upgrade &

Homogeneous

Copy

Target

MAEMADAST64

SAP4.6c/4.7

Transition

Upgrade

In 2006: Upgrade&

Transition&

Unicode Conversion

MAEMADAST64

SAP5.0

Transition to HP-UX/Integrityvia HPSTM

EVAXPHP-UX

IA64

SAP5.0

UpgradeUpgrade

Not recommended!


MAEMADAS

Source

T64

SAP<4.6c

SAP/Tru64 Unix Investment Protection

EVAXPHP-UX

IA64/PA-Risc

SAP4.6c/4.7

HP-UXPA-Risc

SAP<4.6c

Target

EMAEVAT64

SAP4.6c/4.7

Transition

Heterogenous Systems

Heterogenous Systems

�Mix and match of Alpha and Integrity/PA-Risc in a SAP System landscape�SAP Note 531069: Heterogeneous Unix - Unix Systems,

supported by SAP and HP

SAP >=4.6c

SAP <4.6c:


www.decus.de


SAP/Tru64 Unix/HP-UX environments

EVAXP

SAP4.6c/4.7

MAEMADAST64

SAP4.6c/4.7

HP-UXIA64

HP-UXIA64

Scenario 1: Add Integrity-based application servers

HP-UXIA64

Scenario 2: Replace the Alpha database servers

T64 T64 T64

SAP4.6c/4.7HP-UXIA64

T64 T64 T64

EMA

T64


SAP/Tru64 Unix/HP-UX environments

EVAXP

SAP4.6c/4.7

MAEMADAST64

SAP4.6c/4.7

Scenario 3: heterogeneous SAP Landscape

HP-UXIA64

SAP4.6c/4.7HP-UXIA64

EVAEMA

Production:

Preproduction:

Development:


www.decus.de




• HP STM project experiences• Tru64/SAP Transition process and HP deliverables• Customer Stories


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


www.decus.de


Data Center consolidation at AudiTransition of AP6 (1)AP6 is a very critical SAP instance

This one controls the production of engines for Audiand the accounting of AHM (Audi Hungaria Motor)

The Database Size was 800 GB, growing to 1.000 GB at the end of 2005 and growing further

Migration constraints:Transition from Hungary to IngolstadtProduction is running 24 x 6Annual statement of accounts

This has to happen between X-Mas and New Year’s EveSo the final migration (including acceptance tests) has been

scheduled to Christmas 2005:starting on 24.12.05 at 6:00 a.m.ending on 27.12.05 at 6:00 a.m.


Data Center consolidation at AudiTransition of AP6 (2)Planning the transition of AP6

In the first run it was planned to do the final migration using ashadow 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 21.12.2005 and postponed it to Eastern 2006.


www.decus.de


Data Center consolidation at AudiSome 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- andpostprocessing, system and user tests etc.) the whole migration took 22 hours.


German CustomerSAP Server Migration ProjectTask: replace a complete AIX-based SAP datacenter

by HP-UX/Integrity at a large German customer.• 62 SAP systems to be migrated• Largest application: 6,5TB SAP BW 3.0B system• Project time: 7 months


www.decus.de


Migration eines grossen SAP BW Systems• DB-Größe : ca 6,5 TB• Datenbank Oracle 9.2.0.5• Source: IBM,7040-681--16 Prozessoren 1,9GHz;

262 GB AIX Version: 5200-02• Target: Superdome IA64 20 Prozessoren 1,6 GHz

152GB


Migration resultsDB Migration activities• Script generation: 2,5 hours• Migration based on HP STM: 21 hoursSAP Post-Migration activities:• Check und Post migration: 2,5 hours• Import Statistics: 6 hours• Enduser tests• Full offline backup to tape (12 hours)• Overall Downtime: 57hours


www.decus.de


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



www.decus.de

Documents

HP Smooth Transition Method 2N02 Decus · SAP System Copy – SAP Methodologies Homogeneous System Copy SAPinst/R3load e.g R/3 - downtime - effort SAPinst/IMIG e.g TB-sized DB - additional