Database migration as part of SUM:
DMO overview and tuning
Product Management CLM, SAP SE
October 2024
Agenda Database Migration Option (DMO) with SUM
What is DMO?
▪ What use cases? Which kind of systems?
How does it work?
▪ Procedure details
How to tune and optimize downtime?
▪ Aspects for technical downtime of DMO procedure
INTERNAL – SAP and Customers Only | DMO overview October 2024 2
DMO and classical migration
Database Migration Option (DMO)
▪ Scenario migration & update of tool Software Update Manager (SUM) for ABAP based systems
▪ SAP’s recommendation for migration target SAP HANA database: use DMO, if possible
(see https://blogs.sap.com/2017/11/22/comparing-sap-migration-procedures-to-sap-hana-database/ )
Classical Migration
▪ Scenario heterogenous system copy of tool Software Provisioning Manager
▪ Requires manual decision on table splitting, productive migration requires certified consultant
▪ Allows to migrate AS Java based systems to SAP HANA DB
INTERNAL – SAP and Customers Only | DMO overview October 2024 3
DMO in a nutshell
SUM use case
▪ Migration for AS ABAP based systems,
using SUM 1.1 (target SAP BASIS < 7.50) or SUM 2.0 (target SAP BASIS ≥ 7.50)
Database Migration:
▪ Migrate a system to a different database type (heterogenous migration)
▪ Or migrate from SAP HANA to SAP HANA (homogeneous migration) if target product is SAP S/4HANA
Procedures:
▪ In-place procedure: database (host) is switched, but Primary Application Server (PAS) host is kept
▪ Move procedures: use DMO to “relocate” complete system (“DMO with system move” and “DMOVE2S4”)
Initially only target database type SAP HANA, now additional targets possible (see SAP Note on DMO)
System Conversion from SAP ERP to SAP S/4HANA uses DMO (if source database not yet SAP HANA)
INTERNAL – SAP and Customers Only | DMO overview October 2024 4
Main DMO Use Cases are listed in the SAP Note on DMO
INTERNAL – SAP and Customers Only | DMO overview October 2024 5
DMO: Business Case
Upgrade and migration in a combined procedure reduces TCO and risks
▪ Combined procedure needs only one maintenance phase (not two)
– Reduces business downtime (TCO), less regression tests necessary
▪ In-place migration keeps application server and System-ID stable
– Low impact on system landscape: only database server is new
▪ Original database is kept, can be reactivated as fallback
– Reduces risk, no restore required, more time for testing before cutover
▪ No necessity for big export file share during migration
– Direct migration transfer without large dump files (using R3load pipe mode)
▪ No need for manual table splitting to reduce downtime
– SUM uses smart algorithm to determine table splitting
INTERNAL – SAP and Customers Only | DMO overview October 2024 7
DMO phases during the procedure
Source SAP
DB System
1 Upgrade Setup SAP HANA
“Prepare” (client, schema, shadow Uptime
repository, …)
Execute Upgrade
2 (until downtime phase)
Time
Enter downtime
Downtime
Note 4 Migrate application data
Source database continues to run,
but is no longer used to store data
-> easy reset possible 5 Finalize Upgrade
6 Start SAP HANA-based system
INTERNAL – SAP and Customers Only | DMO overview October 2024 8
DMO In-place procedure
▪ DMO is the combination of update and migration,
potentially with Unicode Conversion (target < 7.50) AAS
▪ SUM runs on PAS host (“in-place”), PAS
SUM starts R3load on that host
SUM
▪ Running SUM on AAS (Additional AS) host is possible
(restrictions apply, see SAP Note on DMO) Update*
Migrate
Benefit: run SUM on host with best resources Any Any
DB DB ‘
▪ „DMO without System Update“:
use case to migrate only, no update of SAP software
(only for target database type SAP HANA)
INTERNAL – SAP and Customers Only | DMO overview October 2024 9
DMO Move procedures (1):
DMO with system move
▪ DMO not supported for data center migration due to latency issues
(source & target database in separate data center)
▪ “DMO with System Move”: DMO with System Move
use case to move complete SAP system
− Allows to switch PAS host
− Allows to migrate across data centers
− Allows to migrate to cloud (IAAS) SUM
▪ Requirements:
− Target database and target PAS are set up prior to start Migrate Update*
− Target database type is SAP HANA or SAP ASE Any SAP
HANA or
DB
ASE
▪ Sequence:
− Start SUM in source, export happens
− Copy and start SUM on target, import happens
▪ Can be combined with “DMO without Software Update” and with “SUM on AAS”
▪ Does not allow to use downtime-optimization techniques (doDMO or downtime-optimized conversion)
INTERNAL – SAP and Customers Only | DMO overview October 2024 10
DMO Move procedures (2)
DMOVE2S4: “DMO move to SAP S/4HANA (on hyperscaler)”, Alternative to “DMO with system move”
DMOVE2S4 allows to use downtime-optimization techniques DMO move to SAP
(doDMO or downtime-optimized conversion), S/4HANA (on hyperscaler)
but it needs a good connection between locations.
1. Install AAS in target
Install the target environment an Additional Application Server (AAS)
which belongs to the source SAP ERP 6.0.
2. Extract and start SUM on that AAS
Start SUM for the conversion on that AAS host.
3. Confirm "ASCS instance move" offered by SUM
SUM detects it is not running on the Primary Application Server
(PAS) host, so it offers the ASCS instance move.
4. Post-activities
Some post activities are required which are described in
On-prem Hyperscaler
the DMO Guide.
INTERNAL – SAP and Customers Only | DMO overview October 2024 11
DMO Move procedures (3) with SUM 2.0 SP 21
Transition paths to hyperscaler with „DMO with system move“ or with DMOVE2S4
On-premise Datacenter / Hyperscaler / SAP ECS Private Cloud
DMO with System Move
DMOVE2S4
SAP S/4HANA SAP S/4HANA
DMOVE2S4 with doDMO
DMO with System Move
DMOVE2S4
DMOVE2S4 with doDMO
DMOVE2S4 with doC
SAP ERP 6.0
SAP ERP 6.0
DMO with System Move
DMOVE2S4
DMOVE2S4 with doDMO
SAP ERP 6.0 DMO with System Move DMOVE2S4 with doC
ANYDB
INTERNAL – SAP and Customers Only | DMO overview October 2024 12
Comparing DMOVE2S4 with “DMO with system move”
DMOVE2S4 DMO with system move
Requires good connection* Can use any connection
Allows downtime-optimization
Only offers the parallel mode
techniques
Requires SAP S/4HANA as target Also non-S/4HANA targets are allowed
Uses R3load pipe mode Uses R3load file mode
Only one SUM process runs, Two SUM processes: one on source &
in target infrastructure one on target, partially in parallel
Target AAS is a “full” instance Target AAS is stub installation
belonging to source system No connection to source system
Source system cannot be used Source system could be used
independent of target system independent of target system
INTERNAL – SAP and Customers Only | DMO overview October 2024 13
* See SAP Note on DMO for requirements
Agenda Database Migration Option (DMO) with SUM
What is DMO?
▪ What use cases? Which kind of systems?
How does it work?
▪ Procedure details
How to tune and optimize downtime?
▪ Aspects for technical downtime of DMO procedure
INTERNAL – SAP and Customers Only | DMO overview October 2024 14
DMO Prerequisites
▪ You have planned the scenario in Maintenance Planner
▪ Including selection of the target release kernel files for the target database
▪ You have provided the download folder with all software archives on the SUM host
▪ You have requested and received the migration key
INTERNAL – SAP and Customers Only | DMO overview October 2024 15
SUM UI First Steps
INTERNAL – SAP and Customers Only | DMO overview October 2024 16
DMO: SUM Start
PAS Host
PAS
SUM is started
Source PRD Instance
Kernel
SUM
PRD REP
Application Data
Source DB Host Target DB Host
INTERNAL – SAP and Customers Only | DMO overview October 2024 17
DMO: Shadow System Created
PAS Host
PAS
Uptime:
Source Shadow system
Kernel is created
SUM
SHD Instance
TGT Kernel
Legende
PRD REP TGT REP
Target Note:
Release For SUM 2.0 SP 08 and higher,
the shadow repository
Source
Application Data is created on the target database
Release
for all migration scenarios
Source DB Host Target DB Host
INTERNAL – SAP and Customers Only | DMO overview October 2024 18
DMO: Application Tables are Migrated
PAS Host
Downtime:
PAS
Source Application tables
Kernel are migrated
R3load R3load
SUM
TGT Kernel
PRD REP Note:
TGT REP SUM uses its own R3load
(part of LOADTOOLS,
provided in SUM archive)
Application Data Application Data
Source DB Host Target DB Host
INTERNAL – SAP and Customers Only | DMO overview October 2024 19
DMO: Update Part
PAS Host
Downtime:
PAS
TGT Target kernel is used
Kernel
SUM
PRD REP TGT REP
Application Data Application Data
Source DB Host Target DB Host
INTERNAL – SAP and Customers Only | DMO overview October 2024 20
DMO: Procedure Finished
PAS Host
Downtime:
PAS
TGT Application tables
Kernel are updated
Procedure finished
SUM
PRD REP TGT REP
Application Data Application Data
Source DB Host Target DB Host
INTERNAL – SAP and Customers Only | DMO overview October 2024 21
Agenda Database Migration Option (DMO) with SUM
What is DMO?
▪ What use cases? Which kind of systems?
How does it work?
▪ Procedure details
How to tune and optimize downtime?
▪ Aspects for technical downtime of DMO procedure
INTERNAL – SAP and Customers Only | DMO overview October 2024 22
Tune and optimize downtime
▪ Downtime is dominated by migration part
▪ Migration is influenced by
− Number of R3loads configured for downtime
− Network bandwidth: use 10 Gbit/s network card, use no firewall
▪ Rule of thumb: migration rate of ~ 300 GB/hours should be possible in standard set up
with an estimated additional ~8 hours for the update part, technical downtime can be estimated
Task is to optimize number of R3load processes
▪ Table split calculated by SUM automatically, based on table size
− Keep source database statistic up to date
Optimize table split calculation by providing table duration files from previous run
INTERNAL – SAP and Customers Only | DMO overview October 2024 23
Downtime optimization: overview
Benchmarking
▪ Use Benchmarking before the DMO run:
quick test, it focuses on migration (no shadow system)
▪ Adjust number of R3load processes during Benchmarking, and during DMO procedure
▪ Use the Test Cycle Option
this allows a fast repetition of only the downtime migration for a test run, no need to start from scratch
▪ Provide the migration duration file from previous run in download folder:
it lists measured table migration duration, SUM will use this for optimized table split
▪ Consider downtime-optimized DMO: migrate large application tables partly to uptime
Test Cycle Option
INTERNAL – SAP and Customers Only | DMO overview October 2024 24
Recommended Procedure
▪ Start with the Benchmarking tool
− Export only mode with 100 % of all tables: log file shows total database size to be migrated
− Export only mode with 10 % of all tables: shows potential bottleneck in source database
− Export & Import mode with 10 % of all tables: first impression on migration rate
− Vary number of R3loads to find optimum, use migration repetition option (test cycle) for fast repeat
▪ Continue with DMO, reuse duration file from benchmarking run, use migration repetition option
− Vary number of R3loads to find optimum, use migration repetition option (test cycle) for fast repeat
− Then keep optimum number of R3load processes fixed during complete procedure
▪ Details are explained on the following page: https://url.sap/91hupn
INTERNAL – SAP and Customers Only | DMO overview October 2024 25
Adapting number of R3loads on the fly
Using the SUM Utilities from the menu
INTERNAL – SAP and Customers Only | DMO overview October 2024 26
DMO Migration Preparation section in SUM Utilities
Table sequence (final and sorted sequence) and Table Splits (Runtime with and without split)
INTERNAL – SAP and Customers Only | DMO overview October 2024 27
DMO Migration Post Analysis section in SUM Utilities
Tail Viewer, Bucket Viewer, and Duration Viewer
INTERNAL – SAP and Customers Only | DMO overview October 2024 28
Table Count and Table comparison check
INTERNAL – SAP and Customers Only | DMO overview October 2024 29
Rescheduling Aborted Buckets (1/4)
Scenario
▪ Processing of a bucket (*) aborts during migration
▪ You detect and remove the reason and want to immediately provide the bucket for processing
Solution
▪ You use the Process Control Center to select the respective bucket
▪ You reschedule the bucket
▪ It will be processed as soon as the next R3load pair is idle
▪ Benefit is that you don‘t have to wait for the SUM error dialog
This is only advised if the error situation is harmless / temporarily
INTERNAL – SAP and Customers Only | DMO overview October 2024
* Bucket: work package for a R3load pair 30
Rescheduling Aborted Buckets (2/4)
2) Select the button
„Reschedule selected“
1) Select the
bucket
INTERNAL – SAP and Customers Only | DMO overview October 2024 31
Rescheduling Aborted Buckets (3/4)
3) A message is shown
INTERNAL – SAP and Customers Only | DMO overview October 2024 32
Rescheduling Aborted Buckets (4/4)
4) The bucket status
changes to „Rescheduled“
INTERNAL – SAP and Customers Only | DMO overview October 2024 33
Uptime Migration (downtime-optimized DMO)
Generally available for system conversions and migrations
▪ Uptime migration for selected large application tables
− User changes are reflected with record-and-replay technology of SUM
− Includes initial and delta migration in uptime, remaining delta migration in downtime
SUM Uptime Ramp Post Business Ramp
Technical SUM Downtime
Processing Down Activities Validation Up
Migration Update
▪ Option is offered on SUM dialog on scenario strategy
▪ Report available to select appropriate tables for uptime migration
▪ Replication monitoring is part of SUM Utilities
▪ Applicable only if source is not yet on SAP HANA database
INTERNAL – SAP and Customers Only | DMO overview October 2024
https://blogs.sap.com/2014/09/08/dmo-downtime-optimization-by-migrating-app-tables-during-uptime/ 34
Further Information for DMO of SUM
Central Release Note
Software Logistics Toolset 1.0 – 1563579
https://me.sap.com/notes/1563579
DMO with SUM 1.1 SP 03
https://me.sap.com/notes/3338911
DMO with SUM 2.0 SP 21
https://me.sap.com/notes/3474707
SAP Support Portal
quick link: /sltoolset
http://support.sap.com/sltoolset
SAP Support portal page on DMO
https://support.sap.com/en/tools/software-logistics-tools/software-update-
manager/database-migration-option--dmo-.html
INTERNAL – SAP and Customers Only | DMO overview October 2024 35
