Beruflich Dokumente
Kultur Dokumente
Frank Powell
Chief Operating Officer
Download the presentation recording with audio from the Symmetry Knowledge Center www.sym-corp.com/knowledge-center
Introducing
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
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
SAP Instance
SAP CI and database Refers to all SAP products (R/3, ECC, SRM, CRM, BI, etc.)
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
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
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!
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
Database
SAP and database software are installed Migration utility imports data
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
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
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
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
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
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
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
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