You are on page 1of 37

Planning a Successful OS/DB Migration

Wednesday February 3, 1-2pm Central

Frank Powell
Chief Operating Officer

Download the presentation recording with audio from the Symmetry Knowledge Center www.sym-corp.com/knowledge-center

Symmetrys 21st Century Approach to Managed Services


Quality proactive support delivered by US-based experts
Accessibility 24x7 direct access to your support team

Affordability highly competitive, fixed price contracts

Lifecycle Support for any SAP application on any platform combination


Implementation Support SAP certified Hosting SAP NetWeaver / Basis administration Security design & administration Upgrade & project support

Introducing

Frank Powell Chief Operating Officer SAP Certified Migration Consultant

Agenda
OS/DB Migration Terminology and Definitions Reasons for a platform change Key considerations after the decision has been made High level overview of the process Sample project timetable and milestones Specific SAP requirements Summary Q&A

OS/DB Migration Terminology and Definitions


Heterogenous system copy
Copying an SAP instance to another server of a different operating system, database, or both

OS/DB Migration
Synonymous with a Heterogeneous system copy and is the SAP process of changing the platform Process of exporting all data from source database and importing to target database

Homogeneous system copy


Copying an SAP instance to another server of the same operating system and database

SAP Instance
SAP CI and database Refers to all SAP products (R/3, ECC, SRM, CRM, BI, etc.)

OS/DB Migration Terminology and Definitions


Client copy or client transport
Copying an SAP client locally or to another server Does not copy client independent objects Not a supported method for changing operating systems or databases

Database refresh
Copying an SAP instance to another server of the same platform, generally from restore of backup tape

Agenda
OS/DB Migration Terminology and Definitions Reasons for a platform change Key considerations after the decision has been made High level overview of the process Sample project timetable and milestones Specific SAP requirements Summary Q&A

Reasons for a platform change


Hardware vendor enhancements
Intel vs. Alpha or PA-RISC vs. Itanium These may or may not be considered Heterogeneous migrations

Performance of current platform not acceptable


Overall CPU performance of architecture Memory limitation I/O limitations

New technology better than what you currently have


Features of a new database version from a different vendor have direct benefits to your IT initiatives

Reasons for a platform change


Lack of administrative resources of current platform or another platform has better administrative tools
The resources that originally install the environment are no longer available and a the new corporate direction is on a different platform Have been unable to find resources to support existing platform

Lower TCO of alternate platform


Personnel Training Licensing costs Maintenance costs

Upgrading or avoiding out of support products


SAP stopped supporting Informix and True64 for example

Corporate standardization or consolidation Divestitures and mergers

Agenda
OS/DB Migration Terminology and Definitions Reasons for a platform change Key considerations after the decision has been made High level overview of the process Sample project timetable and milestones Specific SAP requirements Summary Q&A

Key Application Considerations


Which platform to choose
Are you running from a platform or to a platform?

Who will perform the migration? Need certified migration consultant. Are there other SAP projects or IT objectives that coincide with this one (ex. Unicode conversion)? What is the timeline? Is there 3rd party support for the products we use on the new platform? May require a change in licensing agreement with SAP. Start this discussion early! Dont want to start an upgrade until 6 weeks after a migration.
Need a stabilization period!

Key Application Considerations


Need to provide adequate time for testing.
Application functionality should not change..however! Include operational tests (backup/recovery, DR, database maintenance) Performance testing

What are integration points of existing systems? File formats may change (carriage returns and line feeds) The migrations should be performed on separate pieces of hardware (almost by definition) Check your versions of supported products carefully May have large impact on operational procedures (e.g. backups schedule or run-times, security, DR plan, etc.)

Agenda
OS/DB Migration Terminology and Definitions Reasons for a platform change Key considerations after the decision has been made High level overview of the process Sample project timetable and milestones Specific SAP requirements Summary Q&A

High Level Overview of Process


Source SAP Instance Target SAP Instance

Database Flat-file Text

Database

SAP is shutdown, but database is running No downtime minimized concept

SAP and database software are installed Migration utility imports data

High Level Overview of Process: Preparation


Contact SAP regarding your contract Select a consultant to perform the migration Develop a project plan Perform a sizing for new hardware Order hardware for new platform Order SAP migration services Submit project plan to SAP for approval Install the new equipment

High Level Overview of Process: Export of source system


Start with a procedure document to record process Run pre-checks and setup steps per migration guide
Any upgrade post processing must be complete (ex. ICNV) SAP data dictionary and database data dictionary must be consistent Database statistics must be up to date Remove failed updates Delete TEMPSE inconsistencies Suspend batch jobs (BTCTRNS1)

Run selective business reports (finance, inventory, etc) If SID changes, all transports must be released! Run migration utility to export source database Review export performance re-run if necessary

High Level Overview of Process: Copy data to target system


Export files ideally should be local to the target machine Export files are approximately 10-20% of database size FTP Backup/restore NFS or Share required for parallel processing

High Level Overview of Process: Import of target system


Use SAP Migration Utility (similar to an installation) Install the database software Install the SAP instance Import data from source system Review import performance re-run if necessary

High Level Overview of Process: Post processing


Check for missing objects Tune System
Modify SAP profile parameters Modify Database parameters Adapt application specific parameter from source system

System level checks (sick) Follow post processing steps per migration guide
Check Batch jobs with target systems Printers Integration points Apply new license must have contract resolved with SAP

Update migration procedural document!

High Level Overview of Process: Considerations


Export and import can take a very long time tune and re-run those steps until timing is satisfactory Database statistics are important to both the import and export processes. Statistics from previous migrations can be exported and imported to save time. Migration tools provide a means of optimizing the export and import process
Package splitting Table splitting Migration Monitor Distribution Monitor

High Level Overview of Process: Considerations


Pilot run (test migration) mandatory Customer ABAP Objects do get copied Customer tables can get copied
Must be defined properly in the SAP Dictionary (ts<xxx> dictionary tables)

If tables or table spaces have been moved, the ts<xxx> tables must have been maintained correctly to avoid errors. If export will be FTPed to a new platform, a binary copy must be done for data files, ASCII copy of all others files. Migration tools do have re-start capability (except if using pipe method) Process can be used to upgrade to higher versions of Operating System or Database (although not considered a OS/DB Migration!)

Agenda
OS/DB Migration Terminology and Definitions Reasons for a platform change Key considerations after the decision has been made High level overview of the process Sample project timetable and milestones Specific SAP requirements Summary Q&A

Project Milestones
Preparation completed New hardware ordered and installed Sandbox (SBX) migration Functional/Operational Testing DEV migration Functional/Operational Testing QAS migration Functional/Operational Testing PRD migration Go-Live

Project Timeline

Sample project plan - Preparation


ID 3 Task Name Duration Tue Apr 15 Predecessors 8 AM 10 AM 12 PM 2 PM 4 PM 6 PM 8 PM Wed Apr 16 10 PM 12 AM

Preparation Phase Check if target OS, DB, R/3 release, language and code page is supported Plan dates for Going Live - Migration Check Prepare project plan and signed contract R/3 Migration Services and send them to SAP SAP approves migration and sends the migration tools and documentation Request adaptation of the SAP license for the target system Request installation package for the target system Check if patches for the target operating and database system are available Check if installation CDs, guides, and installation notes are available for the target system Hardware installation of the target host and system network installation Adapt operating system parameters on the target machine Set up remote access to the source and target system Determine customer migration ID (see R/3 Heterogeneous System Copy)

22.5 days 0.25 days 2 0.25 days 4 3 days 5 5 days 6 5 days 7 5 days 8 0.25 days 9 0.25 days 10 2 days 11 0.25 days 12 1 day 13 0.25 days 14
Symmetry

Symmetry

Symme

10

11

12

13

14

15

Sample project plan - Analysis


ID 17 Task Name Duration Wed Nov 14 Predecessors 8 AM 10 AM 12 PM 2 PM 4 PM 6 PM 8 PM Thu Nov 15 10 PM 12 AM

Analyze the source system Distribution of file systems/raw devices on disks; NFS file systems, links, etc. Database configuration (number of log files, size of tablespaces/dbspaces) Configuration of the SAP System, distribution of central instance and dialog instances CCMS configuration (operation modes, profiles, etc.) Interface to other applications/machines Backup strategy Batch jobs - which jobs are assigned to which host? Analyze the source system

18

139.75 days 1 day 15 0.5 days 18 1 day 19 0.5 days 20 0.5 days 21 0.5 days 22 0.25 days 23 6 days

19

20

21

22

23

24

25

Symmet

Sample project plan Test Migration

Sample project plan PRD Migration

Sample project plan PRD Migration

Agenda
OS/DB Migration Terminology and Definitions Reasons for a platform change Key considerations after the decision has been made High level overview of the process Sample project timetable and milestones Specific SAP requirements Summary Q&A

Specific SAP requirements


Must use SAP migration service to obtain support during migration process
The SAP Migration Service is fee based
May use service contract checks for this also

Provides go-live checks before and after production migration Technical support during migration process Review of customer migration project plan Migration tools are provided free of charge Test, sandbox or POC migrations can be done without SAP involvement

A certified OS/DB Migration consultant must participate in the project Migration from any certified platform to any certified platform is supported! SAP license agreement must be changed if necessary

Specific SAP requirements - Options


For extremely large database (2TB+) SAP offers an Incremental Migration service that may be required If only changing operating system and not the database
in some cases database tools can be used
Example: moving from AIX/Oracle to HP/Oracle

in rare instances, like endian system types, database restore may be used
MaxDB Endian is the ordering of data within the bytes and bits of data, either left to right or right to left.

If choosing any method other than the standard Migration tools and process, get project approval from SAP in advance. Its required anyway!

Agenda
OS/DB Migration Terminology and Definitions Reasons for a platform change Key considerations after the decision has been made High level overview of the process Sample project timetable and milestones Specific SAP requirements Summary Q&A

Summary
Big Undertaking choose wisely and for good reasons Plan ahead
Hardware lead-times, testing, runtime of migration, impact to business can be significant

Get your migration partner onboard early Contact SAP at start of the project
Migration support License agreement

Look for a firm that will fix-bid the project Insist the process be well documented

Download the presentation recording with audio from the Symmetry Knowledge Center www.sym-corp.com/knowledge-center

Michael Haase
Phone: (414) 238-2341 Email: mhaase@sym-corp.com