SAP Migration to Novell Linux - docshare01.docshare.tipsdocshare01.docshare.tips/files/21183/211831612.pdfSAP Migration to Novell Linux ... customers a smooth transition from “Unix”

SAP Migration to Novell LinuxValue Proposition and Process

Global Fujitsu SAP Competence Center Walldorf, June 2009

Executive Summary – SAP Migration

Project Details: definitions, requirements, check services

Standard SAP OS/DB Migration: project phases and steps

Fujitsu Migration Services

Agenda

© Copyright 2009 Fujitsu Technology Solutions1

Executive Summary – SAP Migration


© Copyright 2009 Fujitsu Technology Solutions

Global and local pool of experienced

and certified migration consultants.

Global Fujitsu SAP Competence Center

supporting the design of the best fit solution.

Standardized & proven toolset for the migration.

SAP OS Migration checks as part of their

safeguarding program (free service).

Fujitsu ensured for 200+ FlexFrame for SAP

customers a smooth transition from “Unix” to “Linux”.

The SAP tools have been used in thousands

of customer projects for more than 10 years.

SAP providing

Fujitsu and partners leveraging

Our project experience

A team to ensure smooth transition

3

More than 200 migration projects

Customers who have successfully migrated to FlexFrame and Novell Linux


"We migrated from HP-UX to Novell Linux within a

FlexFrame for SAP environment back in 2004. To

be perfectly honest it was simpler than expected,

even with lower efforts on our side than for a usual

SAP upgrade project. The standardized toolset

and services from SAP plus the expertise from

Fujitsu and our System Integrator ensured a very

smooth transition - on time and within budget.“J.G.M. Kroon, ICT Architect, ICT AS Solutions CC, TNT

Post

““Fujitsu even took care of problems they were not even responsible for. Our experience was really very positive.”Joachim Friedemann, Team Manager Hosting and Database Technology, Rechenzentrum Leipzig e.V.

“Without exception, Fujitsu delivered exactly what was promised in terms of technology and cost.”Christian Baier, IT Manager SAP Base, REHAU AG + Co

Aerospace & Defense

Automotive

Banking & Insurance

Chemical

Consumer

Engineering,

Construction &

Operations

4

SAP migration: overview

History. 15 years ago SAP identified the need for a standardized migration processdue to:

New platform decisions (x86) in a customer data centers

Mergers & acquisitions

Objective. Ensure a smooth transition via:

Standardized toolset

Support services

Result. SAP OS/DB Migration Check as part of SAP’s Safeguarding program. This service is part of standard SAP maintenance contract.

Availability. Toolset available for all major SAP components:

R/3 3.0D, 3.X, 4.X, ECC5, ECC6…

BW, CRM, SCM, SRM,…

Experience:

Thousands of migrations between various platforms (incl. TB databases)

All major SAP consultants offer required Migration Services


SAP OS/DB Migration Check

Description:

The OS/DB Migration Check is mandatory when migrating a productive system. The service delivery then includes all systems in the system landscape conenrned.

If full support for the migration is required (be it a production system or not), the services of a technical consultant with special certification for OS/DB migration must be ensured.

Value proposition:

SAP OS/DB Migration Check minimizes technical risk involved in an operating system and/or database migration and avoids unforeseen costs that can occur during the migration.

Benefits of SAP OS/DB Migration Check :

Efficient, technically robust operation of the new operating system and/or database is achieved with minimum cost

The migration project is accelerated to get a faster return on your investment

Expensive system downtimes during the migration are minimized

System resource usage is optimized to make the most of your IT investment


Migration steps: high-level

1. Select your preferred partner for the migration project -> SAP certified migration consultant

2. Initiate SAP OS/DB Migration Service with SAP

3. Run Remote Project Audit Session

4. Define joint migration plan

5. Execute test migration

6. Run analysis session (4-6 weeks before final migration)

7. Migrate non-production environments

8. Execute final migration

9. Run verification session (2-4 weeks after migration)

Project timeline: from 6 weeks to 3 months depending on the number of SAP systems to be migrated and availability to test and access the systems.


Project detailsDefinitions, requirements, check services


Definitions

Homogeneous System Copy

The copy of SAP system to another hardware with the same OS and database is called a homogeneous system copy. -> No change of DB and OS

Heterogeneous System Copy = SAP OS/DB-Migration

If the target SAP system will run on a different operating system (OS) and/or a different database system (DB) as the source SAP system, then this is called a heterogeneous system copy. -> Change of DB and/or OS

UNICODE Conversion

An SAP System is converted to UNICODE during a system copy. This can be a homogeneous or heterogeneous system copy.


Successful Migration - Requirements(1)

The Migration has to be done by a certified SAP Technology Consultant for OS/DB migrations:

Certified Technical consultant (at least 4.x)

Special certification for migration (TABC92)

Consultants are on SAP’s migrations consultant list

Experience in heterogeneous system copies (migrations)

SAP data dictionary knowledge

Advanced knowledge of the source database

Advanced knowledge of the target database and operating system


Successful Migration – Requirements(2)

Establish SAP Migration Project Team

Migration Consultant

Project Manager internal/external (depending on project)

Customers technical Consultants (system administrators)

Customers application Consultants (developers)

Customers Power Users for tests and functionality checks

Customers IT management

The migration partner and customer are responsible for the migration. SAP provides back-office support only



Detailed project plan for migration has to be sent to SAP

Order the new system hardware based on a proper sizing

Order R/3 license to reflect the new platform data

Order an OS/DB Migration Kit (Mat.-No. 52002792); this is platform independent(release <= 4.6, from 6.x the tools are on the Installation Master)

Order an Installation Kit for the new platform

Order SAP Migration Check Services for a productive system

Test/migrate the functionality of external interfaces and other applications

Printing system, archive, job scheduling, etc.

External connections (ALE, RFC, NFS, …)

Integrate the migrated system to customer’s High Availability, Backup and System Management solution

The source system has to be available 4 weeks after the live migration



SAP’s prerequisites for the SAP OS/DB Migration Check

SAP systems must be SAP R/3 3.0D or newer

The platform combination chosen is supported by SAP http://service.sap.com/platforms

Remote connection to SAP and an installed SAProuter

SAP EarlyWatch Alert should be running

SAP strongly recommends an implemented SAP Solution Manager


SAP Migration Check Services (I)

Remote Project Audit

Customer completes a questionnaire before the Remote Project Audit is scheduled

Information from the questionnaire is used to determine:

The necessary precautions for a smooth migration

If your requirements are realistic and can be met

Content

Collection of general company data

Checks if the new OS/DB combination is supported by SAP

Checks planning dates for non-productive and productive systems

Checks if the technical consultant is registered as a certified technical consultant with additional certification for OS/DB Migration and fulfills therequirements for executing OS/DB migration projects


SAP Migration Check Services (II)

Analysis Session

Checks whether current hardware is sufficient for the target system

Takes place four to six weeks before migrating

Performed on the source system

A report indicates whether hardware is sufficient and if parameter configuration is necessary

Analyze the performance of your system with respect to the average response times and total workload. The following is analyzed in detail:

Transaction profile check

Top time transactions by response time

R/3 table buffering


SAP Migration Check Services (III)

Verification Session

Checks the new operating system and/or database to verify the assumptions from the Analysis Session

Occurs two to four weeks after migration of the production system

Performed on the target system

Final report confirms configuration and makes recommendations for improvement

SAP prefers to schedule the service sessions well in advance. Thus service contracts should be signed as early as possible.


Standard SAP OS/DB MigrationProject Phases and Steps


Standard SAP OS/DB Migration

Project Phases and Steps:

PreparationThe preparation phase begins with the decision to move to a different OS or DB platform. At the end of this phase the equipment is installed, all key players are involved and a project plan is ready.

MigrationThe migration phase covers the actual system migrations, first a series of test migrations (repeated until the process is fully under control), followed by the “live” migration of the development, QA and production system.

Follow-upThe follow-up phase begins when the entire SAP landscape is operational on the new platform, and covers post-migration, validation and support activities.


Project Steps - Preparation (I)

Item Tasks Responsibility Remarks

1. Decision to migrate Customer Customer must carefully assess the impact that this change will have on his company’s IT.

2.Contact hardware and/or

DBMS vendorCustomer Proper sizing is a crucial task in the migration process.

3.Contact SAP contract

adminCustomer SAP must be informed to adapt the license.

4.Order OS/DB Migration Kit

(<= 4.6)Customer

Up to 4.6 migration tools are in the migration kit. From 6.x the tools are on the Installation

Master.

5.Order OS/DB Migration

Check ServiceCustomer

SAP will deliver three service sessions, two before and one after the productive migration.

This is only required for production systems.

6. Select migration partner Customer A Certified Migration Consultant is mandatory.

7. Inform key playersCustomer/

Migration ConsultantManagement, development, key users, technical personnel, etc. should be informed.

8. Create project planCustomer/


The project plan should contain information on: HW installation and configuration, timing for

test- and productive system migrations, user acceptance tests, printer configuration, external

communications and interfaces, backup and recovery, clustering and high availability.


Project Steps - Preparation (II)

Item Tasks Responsibility Remarks

9. Return SAP questionnaireCustomer/

Migration ConsultantWith the information of the project plan return the questionnaire to SAP.

10.Order equipment (HW

migration)Customer Review the configuration with the migration consultant.

11.Install equipment (HW

migration)HW partner The HW must be installed and the OS configured in compliance with the requirements of SAP.

12. First SAP check session SAPIn the Remote Project Audit session SAP uses the information provided in the questionnaire to

determine that your configuration fulfills all the requirements.

13. Adapt project plan based

on SAP feedback

Customer/


When SAP returns the report of the Remote Project Audit, the necessary technical and / or

planning changes have to be made.


Project Steps - Execute Migration


The success of the productive migration depends highly on the quality

of the previous test work.Migration Consultant

Migrate productive

system9.

Migrating the QA system is optional. QA can also be rebuild on the

target system through a homogenous system copy of the productive

system.

Migration ConsultantMigrate / Copy QA

system10.

Custom ABAP code may contain features that are platform-

dependant, e.g. Native SQL.

Customer/

Migration ConsultantABAP developer tests4.


SAP

Customer/


Customer/


Customer/



Responsible

The development system is usually the first system of the live

landscape to be migrated.

Migrate development

system7.

The SAP Analysis Session will check whether the HW is sufficient for

the target system.

Second SAP check

session6.

The key application users must define a set of business reports, which

will validate the consistency of the data.User acceptance tests5.

It is important, that during the test migrations, where downtime is not

yet an issue the system is rigorously tested and tuned.

Technical

configuration and

tuning

3.

A start-to-finish guide on how to carry out the migration. It should also

contain a procedure handbook which describes the problems not

mentioned in the standard documentation.

Design / improve

documentation2.

Proper testing is absolutely crucial for the success of the project.

As a rule of thumb, two test migrations for a productive system should

be enough. Two weeks between test and live migration is a minimum.

Perform test migration1.

RemarksTasksItem

21

Project Steps - Follow-up

Item Tasks Responsible Remarks

1. Monitoring, tuning, supportCustomer/


The system will still need more than the usual attention after the go-live. Performance

monitoring is important in this phase.

2.Final SAP Check Session

(GoingLive Check)SAP

The third SAP Check Session is the Verification Session takes place between two and six

weeks after the migration of the production system. The assumptions of the Analysis session

are verified and the session also identifies and provides corrective advice for any bottlenecks

and problems observed in the system.

3.Keep old system as

reference

Customer/

Migration ConsultantThe old target system should remain available for several weeks after the migration.





Project Management

Solution Concept

Inspection ServicesTool based Assessment

Solution Preview

Service Level Management

Consult Design Build MaintainOperate

Technical IT Infrastructure Services

AssessmentIT Infrastructure

Solution Specification

Migration Specification Migration Service

Upgrade Services

Audit Service

Go Live Services

Solution Support

Financial TCO and ROI Services

TCO = Total cost of ownership

ROI = Return on investment

ROI Estimate ROI Predict ROI Deliver

Operational

Specifications

Business Critical Computing (BCC) Services

Customer Briefing

Solution Implementation

Customer specific Trainings

Strategy Workshop

Inspection ServicesTool based Modeling

Inspection ServicesTool based Verification

Hardware Installation

Operational

Implementation

Configuration & Sizing

Proof of Concept Rollout Services

Operational Services

Service Packs

Service Contracts

Software Services

Service Portfolio for SAP IT Infrastructure


TCO / ROI Evaluation

24

Fujitsu Migration Services (I)

Migration Specification

Our "Migration Specification" Professional Service provides you with a detailed concept for migrating your SAP systems to your future SAP IT infrastructure.

The "Migration Specification" Service covers three phases:

Phase I: Workshop for coordinating the "Migration Specification"

Phase II: Creation of the document "Migration Specification SAP IT Infrastructure"

Phase III: Acceptance of the "Migration Specification" by the customer


FSC Migration Services (II)

Migration Service

Migration of the application from the source system to the target system

Migration services includes:

Basic Preparation

Implementation in accordance with the documentation "Migration Specification for SAP IT Infrastructure"

Follow-up activities in accordance with SAP guidelines and the "Migration Specification for SAP IT Infrastructure"


[email protected]

Global Fujitsu SAP

Competence Center

mailto:[email protected]


Documents

SAP Migration to Novell Linux - docshare01.docshare.tipsdocshare01.docshare.tips/files/21183/211831612.pdfSAP Migration to Novell Linux ... customers a smooth transition from “Unix”