Migration Monitor - How Are You Using It?

Question

Hello!
In this short discussion, you can help us to better understand how you are using the Migration Monitor – this better understanding would help the team responsible for this tool to adapt their automated tests accordingly and would also influence the future development decisions in this area.
What is the Migration Monitor?
The Migration Monitor is part of the software provisioning manager as of SAP NetWeaver 2004 SR1, but can also be executed manually. It uses the EXT, WHR, STR, TPL files to control the unload and load, to accelerate the load by automatic parallelization, and to generate the R3load task and command files (TSK and CMD files).The Migration Monitor does the following:
Creates R3load command files
Creates R3load task files if required
Starts R3load processes to unload the data
Transfers packages from source to target host if required
Starts R3load processes to load data as soon as a package is available
Informs the person performing the system copy in case of errors
How Do You Use the Migration Monitor?
Only for sequential unload and load - that is, you first unload to a local system, transfer the export directory to the target host, and then load using this directory.
For parallel unload and load:
a) Unload and load using a shared network directory
b) Unload and load using transfer by FTP
c) Unload and load using sockets
In your reply, please just name your preferred option (1, 2a, 2b, or 2c) – and why you prefer it.
Thanks a lot for your support!
Boris

Answer 1

Boris,
Options - All three but mainly Option # 2.
Option # 1 - To dynamically increase the number of parallel process from Source system. But in case of homogeneous system copies with massive database sizes, the database proprietary methods comes in handy than the R3load procedures.
Option # 2 - To reduce downtime in migrations (hetero combinations) thru parallel export/import of data loads.
Hope it helps.
Regards,
Srinivas K.