- Both the heterogenous system copy of Software Provisioning Manager (SWPM) and DMO of SUM support the migration to SAP HANA Database
- Both SWPM and SUM trigger R3load for the export from the source DB and the import into the SAP HANA DB
- But DMO has both R3loads running on the same host: on the primary application server (PAS, fka central instance CI)
(see DMO: technical background)
The "classical migration" (heterogenous system copy of SWPM) uses either the file mode or the socket mode.
Using the file mode, the data are exported, and written into a file, using compression. The file is transferred over the network:
Using the socket mode, the data are exported and transferred over the network:
Now with DMO, both R3load are running on the same host, and they communicate using the main memory of that host, using the pipe mode:
Even with DMO, it is possible to switch to the file mode. The R3load exports the data into a temporary file of limited size. As soon as this file is processed and the data are imported into the target DB, the temporary file is deleted.
- No compression is used for creating the file
- For windows OS, the pipe mode is currently not working, so the file mode is used per default
- Switch to file mode is possible by setting the parameter "/clone/method" to "file" in a (new) text file ?SUM\abap\bin\SAPup_add.par -
but I have no scenario when you would want to switch from pipe to file mode
Note: for SUM SP09 and SP10, the parameter is "/clone/method" (for SUM SP11, it will be renamed to "/clonepar/method").