Scenario

With Software Update Manager (SUM) 1.0 SP 20, 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”.

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 2377305 for DMO with SUM 1.0 SP 20.

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

To report this post you need to login first.

20 Comments

You must be Logged on to comment or reply to a post.

  1. Dharmendra Kumar

    Hi Boris,

    Thanks for this blog.

    I’m closely following SUM and DMO update from SP19 to SP20.

    Can you please confirm –

    1.With SP20, Is cross data center migration supported, from on-premise to Azure, AWS, etc..?

     

    2. Target DB would be HANA, Source is MaxDB in my scenario and with HANA as target DB, I believe we must have

    Linux  as OS for PAS, however can we have other OS like windows for AAS, within same landscape. So, HANA and PAS will run on Linux and AAS on Windows?

     

    Regards,

    Dharmendra Kumar.

    (0) 
    1. Boris Rubarth Post author

      Hi Dharmendra Kumar,

      thanks for your comment.
      1) This is what I tried to express with
      “With this use case, it is possible

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

      2) Concerning the (important) details, my recommendation is to check the respective note.
      As of now, this is SAP note 2377305 for DMO with SUM 1.0 SP 20, and target PAS has to be on Linux. Concerning the setup of AAS on windows, this is not determined by DMO – I guess it works, but you will have to check PAM on this.

      Regards,
      Boris

      (0) 
  2. Dharmendra Kumar

    Hi Boris,

    Point 1 is closed, – understood with SP20 cross DC migration is supported.

    For point 2, I should have NOT put here. I totally agree DMO has nothing to do with OS, and PAM is right tool to check.

    Thanks for your reply.

     

    Regards,

    Dharmendra Kumar.

     

     

     

     

     

    (0) 
  3. Nicholas Chang

    Thanks Boris! Been waiting and nice to have feature! Thanks for your team on the ongoing improvement and innovation.

    one question, any idea how big is the “SUM” directory to transfer if using serial mode? since all the contents are written to the dir *ut*, *dt*, compare to export dump on classical migration?

    And source system downtime starts once enter migration export phase?

    Hope to hear from you,

    Thanks,

    Nicholas Chang

    (0) 
    1. Boris Rubarth Post author

      Hi Nicholas,

      “how big is the SUM directory” -> how big is your database? 🙂

      Both SUM as well as SWPM (classical migration) trigger R3load to export the data (export dump). So for this approach, SUM will trigger R3load using the file mode instead of pipe mode, of course.

      Source system downtime starts once we enter the downtime 🙂 … in uptime, the repository is already exported, like for Standard DMO (where repository is already migrated to target DB during uptime).

      Regards, Boris

      (0) 
  4. Nicholas Chang

    Hi Boris,

    “Both SUM as well as SWPM (classical migration) trigger R3load to export the data (export dump). So for this approach, SUM will trigger R3load using the file mode instead of pipe mode, of course.”

    Does it means we’ll expect the SUM directory size is around the size with export dump by SWPM, taking in all the compression. For classical migration export dump, normally the size is around 20-30% of the DB size. Is it the same apply to export with SUM?

     

    Below pic is taken from the the guide for serial approach. Based on the explanation, looks like the source system are entering downtime once it start migration export on source db, to prevent any changes on the system while the contents are being exported?

    And the exported contents are only start importing into target HDB once the “SUM” directory is moved to target PAS?

     

    Thanks,
    Nicholas Chang

    (0) 
    1. Boris Rubarth Post author

      Hi Nicholas,

      the export files are created by R3load for both tools SUM and SWPM, so yes: the size is similar.
      The sequence of processing concerning migration is (for serial approach):
      • in uptime, development lock is set, shadow repository is created on source system
      • shadow repository is then exported (still uptime)
      • downtime starts, application tables are exported
      • SUM folder has to be copied to target landscape
      • you start SUM run in target landscape, it imports shadow rep and app tables
      Regards, Boris
      (2) 
  5. Gilberto Gangarossa

    Hi Boris. great blog, and very intresting topic.

    Reading the note 237738, I have a doubt about the step below

    ——————< D033068 02/JUL/14 >————————————-
    A new BR*Tools package is required for update or upgrade to NW 7.4 SP08 and higher
    If you want to update or upgrade your SAP system to SAP NetWeaver 7.4 SP08 and higher, install the latest
    BR*Tools package (7.40 patch level 10 or higher) beforehand.

    The new BR*Tools 749 are supported only  for AIX 7.1, but the operating system release of my source system is AIX 6.1.

    So I can’t install the new BR*Tools 749 (R3load, ecc ..)  on my source system, which is a prerequisite to start the Upgrade/Migration !

    I’m I rigth or it is a false problem ?

    Thanks in advance

     

    (0) 
    1. Boris Rubarth Post author

      Hi Gilberto,

      my information is that BRTOOLS are downward compatible – do you have a source that states something else?

      Regards, Boris

      (0) 
      1. Gilberto Gangarossa

        You rigth, a little explanation of what we are doing:

        Upgrade to ECC (HCM) EHP8 from ECC (HCM) EHP4 and move fron Oracle to HANA and from AIX 6.1 to SUSE 12.

        Now, we will execute the SUM SP 20, for system move with DMO, on the source system (AIX 6.1) wich we guess it will use the kernet 7.49 (ie.. R3load) , that is certified only for AIX 7.1.

        Our concern  is that is not possible unless we upgrade the Operating System of the source from AIX 6.1 to 7.1, which is not possible anymore, sigh sigh …

        Thanks for the qick response

        (0) 
        1. Boris Rubarth Post author

          Hi Gilberto,
          OK, now I got it … yes, there are these dependencies, as even for “DMO with System Move”, the shadow system (which is on the new release) is created on the source system.
          Regards, Boris

          (0) 
  6. Manas Srivastava

    Hi Boris,

    I was trying to use SUM 20 with system move option in my scenario where we have to migrate from BW 7.31 SP05 on SQL (On Prem) to BW 7.31 SP05 on HANA (in AWS). When i started the SUM tool it asks for stack.xml file, to bypass this since I was not planning to upgrade i used the option for using SUM for only migration by creating SAPup_add.par and adding migration_only = 1.

    Now the Extraction phase completed but I did not get any dialog screen in the phase PREP_INPUT/MIG2NDDB_INI. Also when I checked logs for this phase it said the Unsupported Target Vector, need atleast NW 740. I copied the target Kernel in the download directory which was provided to SUM.

    Do you have any inputs for this?

    Thanks,

    Manas

    (0) 
    1. Boris Rubarth Post author

      Hi Manas,

      according to SAP note 2377305 for DMO with SUM 1.0 SP 20, BW needs target release 7.40 or higher for DMO, but your target release is 7.31.

      Regards, Boris

      (0) 
  7. Arne Knöller

    Hi Boris,

    Thank you for sharing the updates! Great development of DMO over the last month.
    The restriction of data center boundaries has been removed with SP20 in note 2377305. My question is, what about the SAP support between on premise –> HEC/cloud providers with “classical” DMO, using pipe functionality for parallel export/import.
    Do you support such a scenario now as well ? Or is the support between data centers limited to the system move option?

    Regards, Arne

    (0) 
    1. Boris Rubarth Post author

      Hi Arne,
      thank you for the feedback, will pass it to the dev team!
      Support for “classic” DMO between data centers remains restricted, as we have this new Option “DMO with System Move” now.
      Regards, Boris

      (0) 
  8. Manoj Joshi

    Hi Boris,

    DMO with SP 20 is really wonderful benefits to SYSTEM move, we are planning to move IBM I 7.1 DB2 NW 731 to SAP HANA 2.0  NW 7.5 on cloud. DMO guide does not  mentioned any specific instruction or parameter optimization for DB2.  Any suggestion or pointer to note please.

    Regards,

    Manoj

    (0) 
    1. Boris Rubarth Post author

      Hi Manoj,
      apart from the guide, the respective SAP notes are to be considered.
      For SUM 1.0 SP 20, these are 2371752 (SUM) and 2371752 (DMO), and the notes referenced in there.
      Regards, Boris

      (0) 
  9. Sachin Digamber Pokalwar

    Hi Boris,

    Thanks for the update, could you also please confirm if we can use DMO for only HANA migration as typically DMO has been intorduced for performing Upgrade + HANA Migration.

    Best regards,

    Sachin

     

    (0) 

Leave a Reply