Hello,
We are looking for solution for Migrating our SAP customers from on-premises to Softlayer cloud.
-All Systems on-premises running on Aix with Oracle/Sysbase DB and same need to migrate to softlayer cloud. So we have heterogeneous migration where OS and DB both going to be changed.
Experts here, can please suggest what suitable method will work in this migration?
-r3load export/import or DMO ?
Kindly help here.
The best approach would probably be determined by other factors.
- Are you going to change any aspect of the source system release, support package stack, EHP, during this migration? If you are not changing anything related to SAP itself, only the OS and DB, then the classic SWPM migration approach would seem appropriate (r3load export/import). This process has been used for years and there is plenty of information/tips in Service Marketplace and on forums about it.
- Using DMO as part of SUM would be applicable if you were bundling in some type of update, then DMO would be best since it combines the update with the migration. This reduces the process to one downtime window and simplifies testing/verification
- As SAP now permits the use of DMO/SUM without applying an update, it still includes many steps from SUM that still makes the process complex. This approach would help if you need to minimize your downtime window since this incorporates a shadow instance, though.
When dealing with relocating an entire SAP landscape, the simplest approach is usually the best.
Hello Paul.
Thanks a lot for your response here. Yes we wanted to change support package stack as well before doing DB migration. Plan is to make stack compatible what HANA DB need and then go for Migration. But yet we are not able to finalize what process to be used here. Yes we are relocating entire SAP landscape, before that:
-Update Software stack on source to make it compatible as per HANA DB needs.
-Then, after that using export/import for data migration.
OS and DB both will be change after migration. We are just thinking to use DMO who can do both (update+migration) at same time but in our internal discussion export/import is getting much favour.
Hi,
if you already have Unicode and your Release is still in Maintenance DMO should be available for your systems and it should meet all requirements for SAP HANA.
Maybe you have to do some prerequisites on Operating-System Level of the Source System. Some customers are e.g. using Windows-Server-Versions that not supported for the Target-Release. But if you only want to import Support-Packages, this should apply to you.
By the way: DMO transfers the Database-Content from your Source-Database to SAP-HANA (in a cloud) over the network (no export dump to disk). So you have to have a working direct network-connection between the servers.
BR
Markus
Hi,
additional information: for DMO-Scenario it's not necessary to have a valid OS/DB-Migration-Certification. If you use "Standard"-OS/DB-Migration with R3load you have to be certified. Using SUM with DMO instead of SWPM allows you to combine Upgrade/Support-Packages and even the Import of Transport-Requests with the OS/DB-Migration Tasks. And finally you have only one downtime, and one project with all the effort included (project management, testing, ...). DMO-Downtime is longer then doing Migration only. Some customers prefer 2 shorter downtimes and simpler projects instead of one "big" project with longer downtime.
BR
Markus
Hello Markus,
Concern here after looking at SAP note.
"After the DMO procedure is finished on the source system, and you have copied the SUM folder from the source to the target application server, extract the SUM archive for the target OS over the SUM folder to replace the executables. Make sure that you use the same SUM version (including patch level) in the source and the target system landscape."
In My case source is AIX and target will be Linux & actually i didnt get this part,
"extract the SUM archive for the target OS over the SUM folder to replace the executables". Do we need to configure SUM at both end i.e source & Target?