SAP system copy On-premises: all involved source/target systems in the company's own data centers - SAP Stuff

Direkt zum Seiteninhalt
On-premises: all involved source/target systems in the company's own data centers
Update more efficiently
Also of increasing relevance to companies is the rapid provision of test data or systems in different data centers or in the cloud. A modern test data solution can implement these requirements in a largely automated manner, reducing manual effort, lowering the susceptibility to errors, and saving time and money.

The number of R3load processes to be started in parallel is specified in the {ex|im}port_monitor_cmd.properties configuration file. The Migration Monitor stores the state of the export or import process in the {ex|im}port_state.properties file. For each package being processed, there is a = line.
Differentiation between homogeneous and heterogeneous SAP system copy
An alternative to this is a refresh using a client copy. The test environment will then be missing audit documents, among other things, but the development objects will remain untouched. The client copy only works from a running SAP system, but it burdens the system with database queries and transfers data more slowly than a system copy. The affected client is not available during the copy process. Since there are no options within the client to select what all should be copied, the runtime is often unacceptable.

With "Shortcut for SAP Systems", tasks in the area of SAP system copying are simplified and can also be automated via the command line interface.


Restarting the target system: After HP System Copy completes the above update, UC4 Automated System Copy starts the target SAP instances so that post-processing can be performed.

SAP Stuff
Zurück zum Seiteninhalt