Copying needs to be done skillfully
Reliable and fast rework after SAP® system copies
Administrators and SAP maintainers in the x86 world under Windows and various Unix derivatives can nowadays choose from a wealth of software solutions for system support. In contrast, administrators in the System i world and SAP support staff in this environment are often left to their own devices. Nevertheless, the special system architecture and the peculiarities of the DB2 database integrated in the operating system, as well as the specific applications, also pose challenges for system tool developers.
The solution does not use software agents. The use of standard protocols for the interaction of tool (client/server) and source system and tool with target system has proven itself, exclusively for the purpose of system copy creation. Whereby the use of a single point of management and control has also proven its worth.
TM-TMS (Transport Manager)
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.
An SAP system copy usually includes both the copy of the database and the copy of the file systems that contain the SAP system. There are several ways to create a system copy of an SAP system, depending on the type of database and operating system used.
Use "Shortcut for SAP Systems" to make a required SAP system copy easier and faster.
When the cause of an abort with error has been removed, the status in *state.properties can be set from '-' to '0', and the package will be processed again (i.e. exported or imported).
Adminsitration passwords (DDIC, DB-Admin, Winadmin), create system snapshots (recovery), perform database import.