1/1

The dual-stack split is relevant for systems combined in a dual-stack, like SAP ERP with SAP
Enterprise Portal. DMO cannot be used for SAP Solution Manager for SAP NetWeaver PI
(classical installation as dual-stack).
The figure, Introduction of DMO Phases, illustrates a brief overview of the DMO phases that
are executed by the SUM tool.
Figure 3: Introduction of DMO Phases
Step 1 includes some preparations that are done, like providing stack.xml, passwords, and
download folder. On the SAP HANA database, the DMO procedure only creates required
users and schema.
Step 2 includes the creation of the shadow repository on the source database. This is still
uptime processing, so the system is available for end users. The shadow repository is then
copied to the SAP HANA database.
Step 3 is the switch to the downtime. The system is no longer available. The source database
is still running, but is no longer used to store new or changed data.
Step 4 is the migration of application data.
Step 5 finalizes the upgrade and migration, like switching the SAP system to the new kernel.
Step 6 starts the SAP system, which is now running on the new database and on the new SAP
software release.
During the complete procedure, the source database continues to run. The DMO procedure
offers an easy reset in case this may be required. As the source database was not changed,
the reset is fast and does not require manual interactions. The DMO reset deletes the shadow
repository from the source database, and all other artefacts are reset as well.