Skip to Content
Author's profile photo Nicholas Chang

Demystifying SAP Database Migration tools (DMO, SystemMove, Classical SWPM) for your SAP HANA migration and Cloud Adoption

 

 

 

This knowledge demystifies SAP Migration tools and its technology to facilitate your SAP HANA migration or Cloud adoption by helping you to define and choose the most appropriate SAP migration tool & strategy.

 

The overview helps us to understand the technicalities, functionalities, comparisons, and the use case of each individual migration tool, and then figure out which to use for your migration, either to private, public clouds, or inter/ intra Data Center.

Updated May 2018:

  • Windows is supported for DMO with System Move on SUM 2.0 SP02 (Source ONLY)

 

Archive:

 

Hope you find this post handy along your SAP HANA migration or Cloud Adoption journey!

 

And most happy to connect if you have any question on your SAP migration journey or Cloud adoption, just leave me a message here or LinkedIn.

 

Regards,

Nicholas Chang

Linkedin: https://www.linkedin.com/in/nicholas-chang-48782821/

 

 

Assigned Tags

      9 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo amit lal
      amit lal

      Very nicely compared all scenarios.. Great Job.

      Regards,
      Amit

      Author's profile photo Nicholas Chang
      Nicholas Chang
      Blog Post Author

      Thanks!

       

       

      Author's profile photo Jonathan Ma
      Jonathan Ma

      Would you have a breakdown of how the host change move works in SUM 1.0 SP21? I am in the middle of a Hana/OS migration of the ERP server. The source system DT export has already finished. However, the destination is only running 1 package while over 300 packages are not completed. In the destination SUM directory, I don't see anything is missing on the migrate_dt directory compared to the source SUM. However, the import was not run on these packages.

      What drives the destination DT import and how SUM keeps track of what packages to load or not? In the old world of migration monitor, there is a property file that keeps track of the loading status of packages. Is there such a concept in SUM?

      I found the new SUM/DMO a total blackbox. Please help.

       

      Author's profile photo Nicholas Chang
      Nicholas Chang
      Blog Post Author

      Hi Jonathan,

      Yes, there's a control for all the package that needs to be imported. I can't recall as i don't have the directory/system with me now. What you can do is browse through *dt* or the *log* directories.

      Apart from that, you can analysis the log files on why there's only 1 package is running, you should get some hints.

       

      Cheers,

      Nicholas Chang

       

      Author's profile photo Abdul Khadar Jelani Golighar
      Abdul Khadar Jelani Golighar

      Nice blog chang..clarified many of doubts about DMO..

      Author's profile photo Alexander Seelert
      Alexander Seelert

      Hej Nicholas Chang

      this is one of the best SAP Blogs about the tooling for SUM and DMO and the possibilities you can perform. But in the last column about DMO and migration_only there is a wrong information. The SUM 2.0 SP02 with migration_only = 1 in the SAPup_add.par gives you the possibility to work without a stack.xml file, but in this case, only HANA is supported and not Sybase ASE. This is a little bit tricky if you careful read SAPNOTE 2537452 first section.

       

      1. Upgrade & Migrate:

      SAP HANA

      SAP ASE

      MS SQL Server (available on request, see details below)

      IBM Db2 for Linux, UNIX, and Windows (DB6)  (available on request, see details below)

      SAP MaxDB (available on request, see details below)

       

      2. Only Migrate:

      You want to carry out only a migration of your SAP system to the SAP HANA database, but you do not intend to update the SAP system, and hence you do not need to provide a stack.xml file. For more information about this feature, see the topic “Using DMO without System Update” in the “2 Planning” section of the DMO Guide.

       

      Author's profile photo Nicholas Chang
      Nicholas Chang
      Blog Post Author

      Hi Alexander,

      Thanks and yes you are right, migrate_only parameter just work for HANA DB and none on other classical db. Cheers.

      Author's profile photo Manoj Kumar D
      Manoj Kumar D

      Hi Nicholas,

      Noticed in SUM1.0 SP22 we can use the source DB as fall back post migration with DMO. Can you confirm this?

       

      "The source database continues to run, remains consistent, and application tables are not modified. It remains as a fallback database for the Reset Option [page 34] throughout the complete DMO procedure"

       

      Thanks in advance.

      Manoj

      Author's profile photo Ambarish Satarkar
      Ambarish Satarkar

      Hi Chang,

       

      This blog has made SL-toolset usage decision for migration to Hana so easy.

      Really appreciate it.

       

      Thanks,
      Ambarish