DMO with System Move - the use case to change PAS ... - Page 3

Boris_Rubarth · ‎2017 May 22

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/

Boris_Rubarth · ‎2018 Feb 03

Hello Sander,

as far as I know, Linux as OS for AppServer is not supported for MS SQL database, pleace check.

Regards, Boris

Muadib · ‎2018 Feb 04

Hello,

Thank you Boris for the very informative blog.

Because of some OS restrictions and limited time to test it, we will not use the DMO with system move, we will stick with the classical DMO. However, I have a question related to reducing downtime during the DMO , if you don't mind.

Here is our scenario :

We are doing a DMO (within the same datacenter) from :

SAP ECC6 ehp8, AIX 7.1, Oracle 12

to

SAP S/4HANA1709, Linux SLES 12.2,HANA 2.0

Because we are not using the "System Move" feature, after the DMO procedure, the HANA Database running on Linux, would be connected to the S/4HANA Primary Application Server and ASCS still running on AIX. :

In our scneario, we would need to sequentially :

Install empty HANA Database on Linux server

Perform the DMO : basically move and transform Data from Oracle/AIX to HANA/Linux

Uninstalll ASCS and PAS on AIX

Install new ASCS and PAS on Linux, and this is where it hurts.

It turns out that installation of a S/4HANA PAS takes times, a lot of time : it takes basically 10 painful hours to create the CDS Views (RUTDDLSCREATE job)

As we have a very tight time window, we are thinking of ways to reduce the downtime.

I was thinking of installing before the DMO starts, not only the HANA Database but also the ASCS and PAS with the target release S/4HANA1709 on the linux machines :

Install empty HANA Database on Linux server

Install ASCS and PAS on target Linux Server

Perform the DMO : basically move and transform Data from Oracle/AIX to HANA/Linux

Uninstalll ASCS and PAS on AIX

At this stage we would have an operational S/4HANA 1709 system running on Linux, saving us 10 hours of downtime

Do you see any problem with this approach ?

Thanks and Regards

Former Member · ‎2018 Feb 22

Hi Anil,

We have same requirement. I know DMO with system move option (aka DMO on Cloud Internally for SAP) is well capable for SoH, BWoH migrations to cloud from on-premise.

But the same can be used for S/4HANA conversions as well?

I do not see any such restriction or feature mentioned in below OSS notes.

2532587 - Add. info. on converting to SAP S/4HANA using SUM 2.0 SP01

2532577 - Database Migration Option (DMO) of SUM 2.0 SP01

Please share your expert comments/suggestions.

BR,

Mukul

former_member184682 · ‎2018 Mar 13

hi, could you please throw some light on the restriction of ‘no-support’ for using DMO (the pipe method) for cross data center migrations (OP to cloud which is the most common customer request today). I understand network plays an important role in such cases – but can SAP offer some guidelines on meeting which they should also provide support?

Using the system move approach involves R3trans export / import which involves a multiple times IO traffic compared to the pipe method which means more time and hence more downtime

Also is the restriction with source OS has to be Unix (and not Windows) still apply? Why does the SUM 2.0 SP01 (2532577) note has no mention about the 'system move' option ?

Appreciate your feedback on this

former_member304879 · ‎2018 Apr 10

Hi Raoul,

i beleive the option you wrote should work and is worth testing.

As part of the S4 conversion, the job RUTDDLSCREATE would anyways be executed.

Regards,

Jayesh

Boris_Rubarth · ‎2018 Apr 18

Hi Chandrakanth,
sorry for the delay.
For standard DMO, having a cross data center migration means that you have source DB and PAS in one data center, and target DB in the other data center. Running DMO will lead to long delay due to network latency. But the pipe mode is not relevant for the network consideration, as R3loads are running on the PAS, and pipe mode is only used between the R3loads.
SAP Note 2532577 has a section on "DMO with System Move", not sure about this question.
Regards, Boris

sputnik136 · ‎2018 Apr 25

Hello all, Hello Boris

When doing SUM with DMO Option with "System Move" at the same time, I have the phisical Shippment from one Host to the other. Does this not extend the "Offline" Phase from now 2-3 hours to a significat bigger time?

thank you for any comment on this!

Kind regards

Christoph

Boris_Rubarth · ‎2018 Apr 25

Hello Christoph,
depends on what you compare...
Doing the physical shipment is done because there is a need for it. So my statement is rather: "DMO with System Move" is faster than other ways to combine database migration with host change.
Kind regards, Boris

sputnik136 · ‎2018 Apr 25

Hello Boris,

Thank you for your fast Response.

Shure, Overall-Time is faster, I guess,

but I planed to use SUM in the first Step with DMO to Migrate from Oracle to Hana, and in the seconde Step to make on a new Windows PAS an Installation with pointing to the hana DB Teanant without Dumping it. (I think there is this possibility with SWPM)

This would give me a first short downtime of 2 hours, and a seconde downtime of (probably) 1 hour when I Switch the PAS.

So when I use the "One Step Way" my offline Phase would start from the Point of the phisical shippment till the coming back online. Is't it?

Kind regards

Christoph

Boris_Rubarth · ‎2018 Apr 25

Hello Christoph,

agree: there are scenarios for which a manual switch of PAS after standard DMO is probably faster than "DMO with System Move", like in your example in which all involved hosts are in the same data center.

Kind regards, Boris

sputnik136 · ‎2018 Apr 25

ohh - thats a pitty - the idea to do this in one step soundet very good !

thank you for your time and good dispute

Former Member · ‎2018 Apr 26

Hi Boris.

Great post! One question:

Source: SAP system running on AS/400 DB2/400 (i.e iSeries, IBM i...) with a single system: 1 server for Central Instance + DB . Without ASCS.

Target: Typical Hana architecture: 1 server for PAS on Linux + 1 appliance hana server Linux for HANA DB.

SUM DMO with option System Move can be used to upgrade and migrate from Source to Target?

If so, the Source system can be used normally after finished upgrade+migration ?

Thanks

former_member294712 · ‎2018 May 09

Hi Boris,

Quick check with you, is it possible to make migrate following systems using "DMO systems Move" with workaround on PAS.

Source DB: Oracle

Source OS: Windows ==> Convert Windows PAS to Linux PAS and remaining AAS and ASCS remain on Windows

Target DB: SAP HANA

Target OS: Linux

Let me know if the above is possible.

regards,

Boris_Rubarth · ‎2018 May 09

Hi Dedi,

I guess we have to clarify what a PAS is ...

My view is that as primary application server, the PAS host includes the ASCS. If you agree, then you can't keep the ASCS on your Windows host, separated from the PAS.

Regards, Boris

Boris_Rubarth · ‎2018 May 09

Hi Javier,

the question whether this approach can be used on your landscape touches several aspects:

source has central instance without ASCS

source OS is AS/400 with DB2

target is distributed installation

I do not see any hurdles with it. You will have to check the respective DMO note to see whether OS and database version are supported.

My view on second question "can the source system be used normally after finished upgrade & migration?":
first, after the "DMO with System Move" procedure is finished, you can't use the system, as it was shut down. Nevertheless you can do a DMO reset for the source system, it restores the system to the status before enterning the downtime. Technically you can use the system then, but changes are not reflected on the target system, and the question on license is open (you now run two systems instead of one).
Regards, Boris

former_member463981 · ‎2018 May 10

Hi Boris

I am trying do a SUM DMO with System Move and I need some clarification on the steps at the Target System.

Here is our scenario / landscape
Source: CRM System 7.0 EHP4 SP3. Red Hat Linux 6.9 / Oracle. Distributed with PAS + DB
Target: CRM System 7.0 EHP4 SP10. Red Hat Linux 7.4 / HANA. Distributed with PAS + DB

At the source
- Run SUM (SUM20SP2) using "/usr/sap/C7S/SUM/abap/SUMSTART confighostagent"
- During the phase PREP_INPUT/MIG2NDDB_INI, I checked "Enable the migration with System Move"
- During the phase MAIN_MIGSERIALSETUP/HOSTCHANGE_MOVE, I left TARGET HOSTNAME <empty> because I want to use option 1. Serial mode.
- I have reached the Phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/HOSTCHANGE_STOP
- I copied the complete SUM directory (/usr/sap/C7S/SUM) to the target host (PAS).
- I have reached phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_NEW/SUBMOD_MIG_SER_IMP/SETEXECSTAT_UTMIG_SERIAL.
- At this phase, I see the "YOUR PROCEDURE IS COMPLETE" message.

At the Target
- Install SAP NetWeaver 7.5 ABAP

I need some clarification on what to do at the Target after the tasks at the Source are done.

In the document "Database Migration Option: Target Database SAP HANA" Section 2.4 Performing DMO with System Move,

4. After the data transfer, the SUM with DMO procedure is complete on the source system, and you continue with the procedure on the target system.

Question: What is the procedure on the target system is the document refering to?

Thank you and best regards.

Edwin

Boris_Rubarth · ‎2018 May 10

Hi Edwin,

sorry, but statement „SUMSTART confighostagent“ does not really start the tool, but creates necessary configuration. You start the tool when you use the URL (via hostagent).

Assuming you have configured the hostagent on the target as well, you use the URL to the target host to start SUM on that host, to continue the procedure.

Best regards, Boris

former_member463981 · ‎2018 May 11

Boris

Thank you for the clarification on the SUMSTART.

Here is a summary of my test migration.

At the Source System:

In Phase:MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/HOSTCHANGE_STOP, I copied /usr/sap/C7S/SUM to the Target System (PAS)

At the Target System

I register the hostagent and start SUM.

It showed Current Phase:MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/HOSTCHANGE_STOP.

I select Next. After a few seconds, it said, "YOUR PROCEDURE IS COMPLETE".

There was no indication that the import happened.

Am I missing something?

Is there supposed to be a startup option for SUM at the target?

The hostname of the source and the target are the same. Is this okay?

Thanks

Edwin

Boris_Rubarth · ‎2018 May 11

Hi Edwin,

hostnames have to be different, guess this is mentioned in the respective DMO note (or in the guide).

Regards, Boris

former_member463981 · ‎2018 May 11

Can you point where in the Upgrade Guide that is? I have read thru the guide. Can't find it.

Boris_Rubarth · ‎2018 May 14

Haven't found it in the guide, so you checked the note then, I hope.
Central place to find the actual guides and notes is http://support.sap.com/sltoolset

former_member463981 · ‎2018 May 14

I can't find it in the Central Note either

2529257 - Central Note - Software Update Manager 2.0 SP02

Can you just tell me which "DMO with Move" note mention about different hostnames during move?

Boris_Rubarth · ‎2018 May 14

Well, sorry but I have to say that in general using DMO without considering the respective Note is not recommended.

It is SAP note 2537452 on DMO with SUM 2.0 SP 02.

former_member463981 · ‎2018 May 14

Thank you. I found my answer.

Raghu1 · ‎2018 May 17

Dear Boris Rubarth,

Could you please advice on my below requirement.
source DB : DB2 9.1 OS: AIX 7.1, SAP Application :SAP ERP ECC 6 EHP 3. we want migrate to HANA Db/Sysbase , OS : Suse Linux , SAP Application to be upgrade to : EHp8 ECC 6.0. and different hardware. how to get the delta data after migrate the source to target.

Thanks,

Raghu

Boris_Rubarth · ‎2018 May 17

Dear Raghu,

sorry, but which delta are you referring to?

Thanks, Boris

JAMpe · ‎2018 May 29

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

Boris_Rubarth · ‎2018 May 30

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

JAMpe · ‎2018 May 30

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

Boris_Rubarth · ‎2018 Jun 01

I have only quoted a part of the note, please read the full statement on that scenario in the note.

Raghu1 · ‎2018 Jun 26

Dear Rubarth,

i am clear after gone thru the DMO master note. thank you for the prompt response.

Kind regards,

Raghu

former_member587126 · ‎2018 Jul 09

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

Boris_Rubarth · ‎2018 Jul 09

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

former_member587126 · ‎2018 Jul 10

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

Boris_Rubarth · ‎2018 Jul 10

Hi Aamrin,

no idea - so use the search in SAP Community or create an incident.

Regards, Boris

former_member587126 · ‎2018 Jul 20

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

simseb · ‎2018 Sep 21

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

Boris_Rubarth · ‎2018 Sep 21

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

simseb · ‎2018 Sep 24

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!

Boris_Rubarth · ‎2018 Sep 25

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

Former Member · ‎2018 Nov 29

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

former_member445035 · ‎2018 Dec 10

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.

Source system running on DB2 and have NW stack compatible for HANA. We will start DMO with 'System Move' option.

We will build target skeleton (NW of HANA).

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.

Launch SUM on target and proceed with import and proceed to Finalization/Cleanup phase.

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.

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

Muadib · ‎2019 Jan 28

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

former_member425851 · ‎2019 Apr 13

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

Boris_Rubarth · ‎2019 Apr 14

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

mario_karrenbrock · ‎2019 May 28

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

Boris_Rubarth · ‎2019 May 29

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

mario_karrenbrock · ‎2019 May 29

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

Boris_Rubarth · ‎2019 Jun 03

Hi Mario,

DMO does in general not support STE as target.

Regards, Boris

former_member607927 · ‎2019 Jun 25

Hi Boris,

when installing the ASCS on the target database, how can we keep the (virutal) hostname?

kind regards

Rainer

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

Scenario

Feature

Approach

Preparation

Enabling the use case

Get Your SAP HANA Idea Incubator Badge Today!

SCN Mission - SAP HANA Quiz Challenge is now retired

Share your #HANAStory and Win