Automate SAP system copies
Challenges with SAP system copies
Checklist for preliminary work: Comparison of database sizes (target system must be the same or larger), comparison of database versions, kernel, host agent (ideally the same software version), dump of kernel files (export via SAPINST), saves download via SWDC, compile RFC connection passwords, inform third-party system administrators, provide memory, hard disk on the system for database and software import. Perform database dump, if necessary with transaction log, if possible with downtime, then without jobs or stop running jobs with report BTCTRNS1. Adminsitration passwords (DDIC, DB-Admin, Winadmin), create system snapshots (recovery), perform database import.
Until now, there has been no functional tool for System i to automate and optimize this task. The enormous resource requirements that arise during a refresh of the SAP QA system really cry out for an optimizing software tool. System Copy from Libelle (LSC) reduces the effort required for these work steps. Although a one-time effort is still required, the system landscape is examined so well that the system copy and any subsequent ones are performed literally at the push of a button. The work that is automated by LSC is in the preparation and post-processing of the files as well as the actual system copy.
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
The Migration Monitor: is a standalone tool implemented in Java, takes over the management and control of the R3load processes, is downward compatible. Use the latest Migration Monitor version of the highest release!
Typically, the "homogeneous SAP system copy" process involves a large number of manual activities. A certain skill level is required for this, which leads to the fact that usually the employees of the SAP Basis department or external service providers realize the system copy. Depending on the structure and size of the systems, this process can take anywhere from hours to several days. In addition to making the target systems unavailable to operations and project teams, system and landscape copies also block SAP Basis administrators. Other challenges include the varying duration and quality (completeness) of the results depending on the processor, time dependency on the employees performing the work, etc..
"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.
More information about the package status in the *state* files can be found in the Migration Monitor documentation.
An SAP system copy is a process in which an exact copy of an existing SAP system is created.