Muhammad Haris' Presentation during Leveraging Cloud Technology seminar at Datacomm

1. Cloud SAP Migration
Muhamad Haris
November 28th 2019
1

2. Cloud SAP Migration
Leveraging Cloud Technology for SAP Infrastructure
2
Discussion Topics:
 SAP Terminology: Migration and Implementation
 Cloud SAP Migration Key Challenges
 SAP Migration Methodology
 Cloud SAP Migration: Key Activities
 Key Benefits of Cloud Services

3. Cloud SAP Migration
SAP Terminology: Migration vs Implementation
3
On-premise Cloud
SAP
SAP
SAP
S/4
HANA
Non
SAP
S/4
HANA
 SAP Migration
 Typically ERP classic running on various database (oracle, SQL,
HANA, DB2, etc.)
 Data is migrated by means of System Copy (Heterogenous or
homogeneous Sys Copy)
 Upgrade&Migration to S/4HANA is possible but not
recommended due to long downtime and migration over WAN
 SAP Re-implementation
 Source system is running on ERP classic while target
server is S/4HANA
 Data from source to target is migrated by means of
data conversion (using HANA migration cockpit)
 SAP New implementation
 Source system is non-SAP while target server is S/4HANA
 Data from source to target is migrated by means of data
conversion (download-cleansing-upload)

4. Cloud SAP Migration
Key challenges
4
The following key challenges apply to cloud migration of SAP workloads
 Adopt SAP migration methodologies
• Heterogenous migration (re-platform) of SAP systems (OS/DB migration)
• Homogenous migration using database backup tools
 Minimal outage window for SAP systems
• Heterogenous migration (re-platform) of SAP systems requires longer downtime
• Database size of SAP system and network bandwidth between on-premise and cloud
provider influence the migration time
 SAP landscape complexity
• Many SAP products which are tightly coupled such as BW-ERP, ERP-CRM, and ERP-PI
• Other on-going SAP projects running together with cloud SAP migration

5. Cloud SAP Migration
SAP Migration Methodology
5
Assessment Design Build&Test
Production
Migration
In this phase, current condition
of SAP will be assessed
including:
1. SAP system landscape
2. Backup and recovery
operation
3. Disaster Recovery Solution
4. SAP Security Architecture
5. Application Integration
Architecture (interfaces)
6. Analyze performance
statistics of on-premise SAP
system (EWA report)
7. Review procedures such
SAP transports, printing,
etc.
8. Network capacity from on-
premise to cloud
9. Analyze SAP migration
approach for all SAP
instances
In this phase, migration
approach can be decided and
SAP system design can be
finalized including:
1. Instance sizing (cpu,
memory, storage, etc.)
2. Review and prepare system
parameters including OS
kernel, Database and SAP
parameters.
3. Design backup and
recovery approach in cloud
4. Design the Disaster
Recovery in cloud
5. Design Security of SAP
infrastructure
6. Register SAP Migration
Check with SAP Global
Support
In this phase, SAP systems are
built based on design document
and migration dry-run of SAP
Production Copy to cloud can be
done. The activities include:
1. Setup instance in the cloud
2. Install SAP System on cloud
3. Create migration cutover
plan for each SAP instance
4. Perform migration dry-run
5. Define and execute technical
(basis) test script
6. Define and execute
functional test script
7. Setup backup solution
8. Test backup and restore
9. Setup and test DR solution
10. Arrange with SAP Global
Support for SAP GoLive
Check Analysis
In this phase, cutover activities
for SAP PRD migration will be
done including:
1. Prepare cutover checklist
2. Finalize test scenario that
will be done during cutover
3. Execute migration steps
(SAP system downtime)
4. Execute Post Migration
activities including selected
technical and functional
test
5. Go or No-Go decision
Post GoLive
Support
In this phase, SAP PRD has
gone-live and it is being
monitored closely. The
activities include:
1. Collect performance
statistics report for
baselining (3 or 6 months)
2. Optimize, and tune sizing
based on baseline
performance
3. Arrange with SAP Global
support to get the
Migration Verification
service (usually a month
after go-live)

6. Cloud SAP Migration
Cloud migration for SAP workloads: Summary of Key Activities
6
1. Finalize migration approach (heterogenous, homogenous migration or fresh installation)
2. Analyze application dependencies (mapping) to determine order of systems to be migrated
3. Execute migration trial-run as early as possible to identify potential issues and resource requirements such as
on-premise h/w and network bandwidth from on-premise to cloud provider
4. Choose moderate sizing for non-production system but higher sizing for Production system
5. Execute operational readiness test: Backup&restore, Disaster Recovery, SAP transports, printing, etc.
6. Execute functional (application) test : SAP interfaces, User access (SAPGUI or webgui), etc.
7. Change all system connectivity using hostname instead of IP address since IP for SAP systems in the cloud will
be changed, but hostname can be kept as is.
8. Always create migration plan for each system to be migrated even if the system is non-production system
including fallback plan in case we have to go-back to on-premise system
9. Identify location of SAP users especially if there are SAP users accessing SAP system from remote area
10. Minimize version changes on OS, SAP and database for SAP system (“like-for-like” migration). Migrate all SAP
instances to cloud first, then execute version upgrade on the cloud if required

7. Cloud SAP Migration
Key Benefits of Cloud Services
7
There are many benefits of using cloud services. Some of the benefits that we obtained during cloud migration of SAP
workloads are as follows:
 Automation
Quick and easy to setup SAP system especially during SAP migration dry-run (simulation)
 Security
During SAP migration test, the system can be easily isolated using security groups
 System Recovery
Faster system recovery with combination of snapshot and database backup
 Asset management
Systems will be tagged with unique identifiers to reduces billing disputes and simplifies asset management
 Hardware Renewal & Maintenance
Reduce investments with purchasing, refreshing hardware, and associated hardware maintenance contracts