Skip to Content
Technical Articles

DMO with System Move – the use case to change PAS host during DMO

Scenario

With Software Update Manager (SUM) 1.0 SP 20 (and higher), a new use case is introduced for DMO of SUM: DMO with System Move. This blog provides an introduction into this use case, which is of course described in the respective DMO guide, section “DMO with System Move”.

Note: you should be familiar with the DMO introduction before reading this blog.

Scenario is that you want to change the host of your Primary Application Server (PAS) instance during the DMO procedure. Until now, this was not possible during DMO.

Feature

With this use case, it is possible

  • to change the PAS host inside your System landscape, or
  • to move your system to a different network area / data center, or
  • to migrate your system from on-premise to HANA Enterprise Cloud (HEC), or other cloud providers

Note:

  • for SAP internal colleagues, this procedure was known as “DMO to SAP Cloud”. It is now available not only for targeting SAP Cloud.
  • “DMO with System Move” works for target database type SAP HANA and SAP ASE.
  • Restrictions are listed in the SAP note for DMO, see http://support.sap.com/sltoolset.

Approach

Preparation

  • Before starting the DMO procedure, you have to set up the new PAS host in the target landscape, in addition to the target database
  • You do not have to set any specific control file or parameter before starting the SUM

Enabling the use case

  • On the dialog with DMO details (like Migration Key), an option “DMO with System Move” is offered.
  • When this option is selected, the SUM will execute some tasks in the source landscape (like export the data from the source database), and afterwards execute some tasks in the target landscape (like Import the data to the target database).
  • In the source landscape, the target database parameters (like database host name) do not have to be provided
  • Once the tasks in the source landscape are finished, the SUM will tell you on a dialog to copy the SUM directory to the target landscape, in which the procedure will be continued. The SUM directory contains all required files
  • Transfer of SUM directory can be done e.g. via network (if possible), or via USB disk.

To reduce the downtime, it is possible to use a parallel mode in which data export and data import is running in parallel. Interested? You have to consult the DMO guide anyhow – the parallel mode is described in there, and is beyond this short introduction.

Kind regards,

Boris Rubarth
Product Manager SUM, SAP SE

[Added on Oct 22 2020]

Please consider the following blog as well:
https://blogs.sap.com/2020/10/22/dmo-with-system-move-with-shd-rep-on-target-db/

180 Comments
You must be Logged on to comment or reply to a post.
  • Hello Boris Rubarth,

    Can we move to Cloud provider using Classic DMO (no System Move) then uninstall PAS and ASCS in source datacenter and then install a new ASCS and PAS on cloud provider?

    Is this technically possible and/or supported? 

    Best regards,

    JAM

    • Hello JAM,

      for standard DMO, this approach is not supported, and we have noted this in the respective SAP note on DMO:

      “Using DMO for a migration across data center is not supported (PAS host and DB host in different data center). …”

      You find the actual note listed in http://support.sap.com/sltoolset.

      Best regards, Boris

       

      • Thank you for the input Boris Rubarth . Let me explain a little more the scenario:

        The system we want to migrate is currently on iSeries platform. We want to move the system to a cloud provider where there’s no iSeries Platform available. Thats why we can’t use the “System move” option.

        So we were thinkg about using the Standard DMO across datacenters until the migration process is done, Not for productive use. After the DMO process have finished, uninstall the PAS and ASCS on current datacenter and then install them in the Cloud datacenter, then Go Live. Can this be supported or work as an exception?

        Best regards,

        JAM

         

         

  • Hi Boris,

    can you brief me about the serial mode of System move.I have selected serial mode and the SUM process is completed in source host and i have moved the SUM directory to target host and it has started in phase MAIN_MIGSERIALSETUP/HOSTCHANGE_MOVE.On my target host it is asking the PAS host and instance number ,so the input should be from my old host or new,when i proceed it search for usr/sap/SID/profile with new host but there is no new profile created yet.Do we need to do anything manually to bring it on the target host?I dont see any special step on guide for serial mode.

    Thanks,

    Aamrin

    • Hi Aamrin,

      all parameters that SUM asks for on target are about target PAS. If you have installed a PAS, then there are profiles created. This is independent on whether serial or parallel mode is used.

      Regards, Boris

       

      • Hi Boris,

        Thanks,i was missing the PAS instance,after installing it worked.

        Downtime migration phase is over  on target host but i am stuck with saplikey issue .here is the log,i tired to delete it manually but it is giving me error”Can’t delete any license keys because of an error when trying to retrieve all records from the store.”

        3 ETQ120 20180710093923: PID 10326 execute ‘~/exe/saplikey -get’, output written to ‘/usr/sap/SUM/abap/log/SAPLIKEY.OUT’.
        3 ETQ122 20180710093923: PID 10326 exited with status 0 ” (time: 0.0/ 0.0/ 0.0/766MB real/usr/sys/maxmem)
        2 ETQ399 Retrieved local hardware key from ‘saplikey’ call as ‘Q1488002337’.
        1 ETQ399 Installing new temporary license for system.
        3 ETQ120 20180710093923: PID 10327 execute ‘~/exe/saplikey pf=/usr/sap/D01/SYS/profile/D01_D00_uscls4hd01cs1 -delete D01 Q1488002337 *’, output written to ‘/usr/sap/SUM/abap/log/SAPLIKEY.LOG’.
        3WETQ122 20180710093924: PID 10327 exited with status 2 ” (time: 1.0/ 0.0/ 0.0/766MB real/usr/sys/maxmem)
        1EETQ399 Last error code set is: Process /usr/sap/SUM/abap/exe/saplikey exited with 2, see
        1EETQ399X’/usr/sap/SUM/abap/log/SAPLIKEY.LOG’ for details
        1EETQ204 Upgrade phase “INSTTEMPLIC_MIG” aborted with severe errors (“20180710093924”)

        In SAPLIKEY.OUT ,we are getting below logs:

        EXECUTING /usr/sap/SUM/abap/exe/saplikey -get
        E
        ===…could not load SSF library /usr/sap//SYS/exe/run/libsapcrypto.so .

        E 543 likey_init_clt: Couldn’t load SAPSECULIB
        (“/usr/sap//SYS/exe/run/libsapcrypto.so”) using function SsfSupInitEx (), rc
        = 10 (no library).
        E 542 likey_init_clt: At least one more attempt to load the SAPSECULIB will
        follow.

         

        Regards,

        Aamrin

          • Hi Boris,

            My issue was resolved .The solution to this was upgrading the kernel files in the /SUM/abap/exe/ directory .After the update I was able to proceed further and complete  my S/4 HANA conversion successfully.

            Regards,

            Aamrin

             

  • Hello Mr. Rubarth,

    We want to perform a really big change on our SAP BW systems and I’m not sure if this is possible with the SAP DMO system move option. Maybe you can give me a hint if our plan is working or not:

    Source: SAP BW 7.4 SP13, on Oracle 11.2.0.4.0 and HP-UX on ia64 machine

    Target: SAP BW/4HANA with HANA Database on SLES 12 and X86 -> completely different server and architecture

    Maybe the migration directly to SAP BW/4HANA is not possible. Then the we got to SAP BW 7.5 on HANA database on SLES 12 and X86. And in a second step with the SAP-BW/4HANA-Starter-Add-On to SAP BW/4HANA .

    Is this possible in general or do we need to make at first a heterogenous system copy from HP-UX to the new Server with SLES 12 on X86. And afterwards use DMO without system move option?

     

    Thank you very much!

     

    Best Regards

    Sebastian

     

     

     

     

    • Hello Sebastian Simon,

      for targeting SAP BW/4HANA 1.0, SUM is not the tool of choice: you use SPAM/SAINT for that step.

      You may consider to use SUM 2.0 for the step from SAP BW 7.4 on Oracle to SAP BW 7.5 on HANA. In addition, you may check if “DMO with System Move” is an option to switch from HP-UX to SLES 12 on X86 in the same procedure.

      Best regards,
      Boris

      • Thank you for your comment. You are right, to SAP BW/4HANA we hve to use SPAM/SAINT.

        But all in all the change from SAP BW 7.4 on Oracle to SAP BW 7.5 on HANA, together with system move to X86 (in one step) is possible, correct?

        Thanks!

         

        • I looks to me as if this should work – please check the details in the respective notes so that we do not oversee any restriction. Regards, Boris

  • Hi Boris Rubarth,

    We are planning to migrate our system to HANA.

    We are running on windows 2008 with MSCS cluster and planning to move S4HANA1809/Suse Linux.

    for moving to S41809, Windows server should be on windows server 2016 but upgrading OS from 2008 to 2016 is 2 step process. 2008–> 2012 and 2012 –> 2016 but In place upgrade is not supported in case of 2008 –> 2012.

    Please suggest do we need to Install Additional Application server on windows 2016 and run SUM from there. Do we need to have ASCS on that new server or upgraded windows 2016 OS.

     

    Regards,

    Nikhil

    • Hello Nikhil,

       

      We are in the exact same setup you described : did you find a solution regarding the installation of an additional Application Server running on windows 2016 OS. :

      Did you need to upgrade the instance hosting the ASCS to windows 2016 OS or was it sufficient to install and Additional Abap Instance on windows 2016 OS

       

  • Hello Boris,

     

    Can we use System Move option and keep Source and Target systems running as end result?

     

    We are required to build new landscape (N+1) on HANA keeping source landscape untouched until Production migration is done. Just to elaborate, we will follow below high level approach.

    1. Source system running on DB2 and have NW stack compatible for HANA. We will start DMO with ‘System Move’ option.
    2. We will build target skeleton (NW of HANA).
    3. When DMO on source reaches to end of HOSTCHANGE_MOVE stage, we will copy SUM folder to target server (considering Serial mode) would be selected.
    4. Launch SUM on target and proceed with import and proceed to Finalization/Cleanup phase.
    5. We assume this will still keep source system in consistent state and choosing ‘Reset’ option on Source will take Source system to original state and both systems would be in usable state.
    6. Further, we will use System Rename feature of SWMP on target system to change system SID. This would be followed up by few post build steps like BDLS etc.

    Another (most recommended) alternative would be to build target first as system copy (on DB2) and then carry out in-place DMO. But just wanted to see if we can follow above approach to achieve same results.

     

    Regards,

    Prasad Desai

  • Hello Boris,

    Thanks for your input in this blog,

    We are moving to azure cloud from Windows 2016/ SQL Server 2008 R2 / EHP4/NW7.01 to Linux/HANA/EHP8/NW75 , planning to use SUM DMO with system move ( PAS from Windows 2016 to SUSE Linux  12 ) using SUM 2.0 SP4, I read the manual and notes , so far I don’t see any restriction, currently I am also testing the process and  at prepare phase and SUM didn’t complain so far  but I am hearing that it is not possible, any restriction on DMO to move PAS from Windows to Linux ? Your reply will be appreciated.

    Thanks , Al Mamun

    • Hello Al Mamun,

      as always, any restrictions are mentioned in the respective SAP note for DMO, currently SAP Note 2644872 (for DMO with SUM 2.0 SP 04).

      You read the note, as I did – I do not see any restriction for your scenario, if you follow the description – but you better check again.

      Thanks, Boris

  • Hi Boris,

    in the features you list:

    • to migrate your system from on-premise to HANA Enterprise Cloud (HEC), or other cloud providers

    DMO with System Move works with a scenario from SAP ECC on premise to HANA Enterprise Cloud (HEC) Single Tenant Edition (STE) to go to S/4HANA as well correct?

    Thanks,

    Mario

     

    • Hi Mario,

      thanks for asking. SUM does not allow to convert an SAP ERP system (contains custom code, modifications, and esp. custom specific customizing) to „Single Tenant Edition“. For a conversion with SUM, the target SAP S/4HANA will always be the on-premise edition.

      Regards, Boris

      • Hi Boris,

        thanks for the quick response.

        Would it work to first do SUM with target S/4HANA on-premise and afterwards perform a DMO from on-premise to HEC “Single Tenant Edition”?

        Or does HEC “Single Tenant Edition” not allow a Database Migration Option and its always build from ground up in STE?

        Thanks,

        Mario

    • Hi Rainer,

      sorry to say that I do not see an easy way to achieve this. SUM does not offer a procedure for this. You may consider to adapt this manually, but I have no complete list of actions to be considered. Editing the /etc/hosts file would have to be done in downtime, the profile files have to be adapted, and maybe service registration as well.

      Kind regards, Boris

    • Hi Tatjana,

      as SAP Solution Manager is based on SAP BASIS 7.40, you would have to use SUM 1.0. The respective SAP Note for DMO with SUM 1.0 SP 24 is 2743782, which lists:

      DMO with System Move is currently not supported for SAP source systems running with Windows operating system.

      So I guess it is not a supported scenario.

      Regards, Boris

  • Hi Boris ,

    We’ve planned to run a conversion towards S/4HANA 1809 of our system (ECC6.0 EHP7 , Windows 2012 , Oracle 12) but our OS is not supported (Windows 2012) and we cannot do an heterogenous system copy before the conversion.

    So we think to use option 2 of note 2696472 – Upgrade/Conversion planning hints for de-supported platforms.
    => Run the Software Update Manager on an additional application server (based on a supported platform) and choose the ASCS Instance Move option offered by the Software Update Manager.
    – So if we install an AAS on our current landscape on Windows Server 2016 , will all the SUM processes run on this server up to the end of SUM (So this new AAS will become the future ASCS/PAS instance)?
    – If no does it mean we need to setup a target landscape and perform all the steps of the System Move option of the guide like preparing system landscape (which means a third server and a lot of additionnal steps) ?
    – When is the ASCS Move : during Uptime (which means impact on source) or during downtime?
    Regards .
    Odane.

     

  • Hello Boris,

    We would like migrate our landscape SAP ECC EhP4 to Ehp7 on Hana 2.0 (with SUM 1.0)

     

    Current system :

    SAP ECC6 EHP4  (NW7.01)

    MS SQL Server 2008  ==> Supported Until 09/07/2019

    Windows Server 2008 R2 (x86_64) ==> Supported Until 14/01/2020

    Datacenter 1

     

    Target :

    SAP ECC6 EHP7 (NW7.40)

    SAP HANA 2.0 SPS4

    Linux Redhat 7.6

    Datacenter 2

     

    I would like migrate on 1 step with SUM/DMO and system Move, but I don’t konw if it’s possible in this case.

    It’s possible to add an AAS on Linux Redhat 7.6 ( connected with SQL Server 2008 on Windows 2008 R2) and start SUM/DMO with System move on this AAS ?

    And when DMO procedure is finish on source system/datacenter, copy the SUM Directory and export dump on target system to continue this migration (ASCS/PAS/ data on Hana RedHat 7)?

    It’s possible to use the workaround indicated on SAPNotes 2743782 ( SUM 1.0 DMO-System Move with windows and sql server desupported on source systems) ?

     

    SAP Notes :

    2696472 – Upgrade/Conversion planning hints for de-supported platforms

    « Run the Software Update Manager on an additional application server (based on a supported platform), do not choose the ASCS Instance Move option, and take care of the system setup manually at the end of the Software Update Manager run prior starting the productive system. »

    1951491 – Minimal DB system platform requirements for SAP NetWeaver 7.4 SP08 :  SQL Server 2012 (min. versions see SAP Note 62988)

    2690361 – Central Note – Software Update Manager 1.0 SP24 [lmt_006]

    « Running SUM on an AAS Running SUM on an additional application server (AAS) is only working if sapcontrol and sapstartsrv are existing and configured properly. »

    2743782 – Database Migration Option (DMO) of SUM 1.0 SP24

    « DMO will keep the application server stable. This means that no switch of application server is possible. The only exception is the “DMO with System Move” scenario, which makes a switch of the application server possible. » « Using DMO for a migration across data center is not supported (PAS host and DB host in different data center). There are no technical restrictions, but it comes with a high performance and latency impact. You may use it at your own risk. No support is provided in case of performance issues or broken procedures due to network/latency issues. Consider “DMO with System Move” instead. »

    « Target Database SAP HANA :MS SQL 2005 (available on request), or a higher version, if target SAP_BASIS is lower than 751 »

    « “DMO with System Move”: Requirements and Restrictions with regards to operating systems: For “DMO with System Move” with SUM 1.0, the OS of the target Application Server has to be Linux. If the source PAS host is running on Linux OS as well, no restrictions apply. However, if source PAS host is not running on Linux OS, you have the following options:

    • SAP source systems runs on Windows OS: These systems are not supported with SUM 1.0. If possible (that is, if it is supported according to PAM), you can consider the previously mentioned workaround where you install in the source system an AAS running on Linux OS. è As a workaround, install on the source system an additional application server (AAS) that runs on Linux OS. In this way, source OS and target OS are identical. »

    « SUM on an AAS: You may not run the SUM on an AAS if ASCS is not yet running separately (such as during the standard DMO procedure). »

     

    Thanks in advance,

    Regards,

    Roby

    • Hi Roby,

      sorry for the delay.

      I am afraid that this scenario does not work, as far as I know it is not supported to run an Additional Application Server on Linux against an MS SQL database.

      Regards, Boris

      • Hello Boris,

         

        OK, Bu is below scenario work?

         

        Source System:

        EHP5

        Oracel 11.2

        Window 2008 R2

         

        and i would like to migrate using DMO with system move and target system would be.

         

        HANA 2.0 on SLES + PAS will be on window 2016 (EHP7 Application)

        Application will ECC6 EHP7

         

        Is that OK?

         

        Regards

        Wajid

         

         

         

        • Hello Wajid,

          please tell me what the result of your investigation is, and which sources you have checked.

          My recommendation is to start with the central landing page http://support.sap.com/sltoolset to find the actual SAP Note 2743782 “Database Migration Option (DMO) of SUM 1.0 SP24” (target on EHP 7 = BASIS 7.40 requires SUM 1.0). In there the requirements for “DMO with system move” are listed.

          Regards, Boris

  • Hi Boris,

    When doing the SUM DMO with System Move option. When precisely can you start the SUM process on the target system?  In the attached screenshot it says you can start the DMO run on the target host but after clicking next it errors because it detects SAPup running on the target.  Is the DMO run on the target supposed to be started later?  It is not clearly stated on any other screens or in the SAP Help documentation.  Thank you.

    Regards, Gabe

     

    /
    • Hi Gabe,

      the screenshot shows the correct dialog: phase HOST_CHANGE_MOVE is the first point in time when you can start to transfer the SUM directory (which means following the parallel mode) and start SUM on target.

      “… after clicking next it errors because it detects SAPup running on the target …”
      Not sure if I understand your situation: you have transferred the SUM directory to the target (as stated on the dialog), then you have used the browser to start SUM on the target, and after clicking Next on the target dialog, you get the error that there is already an SAPup running? Then someone has already started it. You should check this and/or create an incident.

      Regards, Boris

      • Hi Boris,

         

        Thank you for the reply.  I transfer the SUM directory from the source to the target.  Then on the target system I start SUM to prepare the target system.  When I go back to the source and click next I get the error below and hit next and returns back to the previous screen.

        ERROR: SAPup already started on target host, must not sync fully anymore!

        I then stop SUM on the target, delete the SUM folder on the target and re-transfer it.  I then click next on the source screen and everything works fine without starting SUM on the target.  I assume I wasn’t supposed to start SUM on the target system yet as the error indicates but the screen on the source says to start it.

        I enter downtime and after the sync finishes I start SUM on the target and the migration completes however I don’t get the benefit of parallel export/import.

        Regards, Gabe

        /
        • Hi Gabe,

          please create an incident, provide all required details like SUM version and logs, and send me the incident number as private message. I will try to follow up.

          Regards, Boris

        • Hi Gabe,

          now I have an idea: you have specified the target host name on the dialog of phase HOSTCHANGE_MOVE. This will trigger the script provided by SUM which tries to do the FULL (initial) sync transfer. But you have manually transferred the SUM directory already, that is why the script throws the error. Which SUM SP version do you use?

          Regards, Boris

          • Hi Boris,

            That is correct.  I manually copy the SUM folder over before clicking next as directed by the dialog in SUM.  After the manual copy finished I start SUM on the target.  I did find the verbiage from the error in the rsync script.  I was using SUM SP3 PL1 due to support for an older source database release.  My guess is this is maybe a bug fixed in a later release?

            Thank you

            Gabe

          • Hi Gabe,
            yes, the dialog was adapted meanwhile.
            Sorry, but I have to add a comment on using an outdated SUM SP version which is out of maintenance (we have SP07 available meanwhile): in case you run into issues, SAP may no longer be able to support you. Even worse: it is possible that there is a good reason that “older source database releases” are no longer supported due to issues with this version.
            Sure I hope that your project works without any issues!
            Regards, Boris

          • Hi Boris,

            Thank you for the information.  Is SUM supposed to be started on the target system on the next step then after SUM triggers the script and does it’s initial full sync?

            Regards,

            Gabe

          • Hi Gabe,

            not sure if I understand your question correct, but this is what the dialog states, and it is explained in the guide. Let me know if there is a specific text part that we should improve.

            Thanks and regards, Boris

             

  • Hi Boris,

    Is it possible to fully or almost fully automate a migration to S4/HANA, using SUM with DMO? If so, would system option be available?

    Source System: EHP6 EHP8 + ASE + RHEL
    Target System:  EHP6 EHP8 + HANA 2.0 + RHEL

    Regards,

    Martim.

  • Hi Boris,

     

    We have a scenarios where we need to consider the DMO with move option, We are moving a AIX based system to HANA DB on cloud along with an upgrade. We would like to retain the same hostname for all the systems including PROD. We need this to avoid effort of changing all the integration to connected Netweaver systems, testing etc. I haven’t seen this use case in the documentation. I would like to check if this is possible with the latest version of SUM tool

     

    Regards

    PK

    • Hi PK,

      I am not an expert on network and host name setup. The respective SAP Note on DMO states

      Short host names for source and target PAS:

      They must be different. Otherwise the Software Update Manager does not start on the target system.

      Note that fully qualified domain names are not affected.

      There was no change in the latest SP-versions of the SUM tool regarding this aspect.

      Regards,

      Boris

    • Hi PK,

      You can always change the hostname after downtime post processing, before releasing the system to functional team and final users. But for sure, you can’t use the same hostname for 2 different servers (even with different IP address) within an SAP process (SUM, SWPM, etc).

      Kind regards.

  • Hi Boris,

    This is a good blog that provides insight on DMO with System Move Option. I have a question, can we use SUM DMO System Move for migrating SAP S/4HANA from One-Premise to other Cloud Providers (Azure/AWS) without any changes to software or OS/DB?

    Thanks,

    Ravinder

    • Hi Ravinder,

      thanks for asking: this is not possible.

      Reason is that DMO as such only supports heterogenous migration cases, as listed in the SAP Note on DMO. This applies to “DMO with system move” as well. SAP S/4HANA is based on SAP HANA, and we do not support HANA to HANA scenarios with DMO or DMO with system move.

      Regards, Boris

       

  • Hi Boris,

    i have a question, we have existing BW application which is running on windows in a separate host and database is running on Hana and OS as linux in another box.

    So we are planning to move the BW Application to a new box which is a windows platform and DB Hana remains Same and once application moves to a new host we need to connect to the same HanaDB and after that we will decommission the old one.

    So which method will be preferable, please suggest.

    Regards,

    Shankar