Import of delta statuses after SAP system copy / restore
Pre- and post-processing
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.
Over 30 productive systems at more than 9 customers successfully copied using IMIG. For the Unicode conversion of a 4.5 TB system (2.7 TB data) a downtime of 16 hours was achieved (including the follow-up work such as reconfiguration, updating DB statistics, generating reports, creating backups, testing the system).
Automatic determination of delta states after SAP system copy/recovery
There are now a number of tools that simplify refresh activities of non-production SAP systems. The tools are imported into SAP systems via transports and enable the data to be copied to be written in. The more precise the selection, the greater the potential savings in storage space and extraction time compared to client copy. As with the latter, the configuration is retained and ongoing development and test processes remain undisturbed.
The demands on your business are constantly changing. For this reason, there is also a need to adapt processes and functionalities. This cannot be done directly in the production system, but must first be extensively tested, which in turn requires data that is as realistic as possible. The SAP system copies required for this are quite time-consuming and complex, but also offer very great automation potential. We support you in the execution of SAP system copies and, within the framework of our partnership with Libelle, we can also set up automation mechanisms for you if you have the need for regular system copies. We are also happy to support you with any data anonymization that may become necessary after such a copy.
"Shortcut for SAP Systems" can considerably simplify and shorten a number of activities within the scope of a system copy or a system refresh. By using this application in conjunction with the information on system-specific tables from the PCA tool, the system-specific data can be backed up and restored after the system copy / system refresh. As a result, many of the activities mentioned here regarding data backup / restore can be performed much more easily; the creation of screenshots and the subsequent manual restoration of the state documented in this way can then be completely eliminated.
Set up ATM jobs: SE38 (000 client, delete transport setup), redistribute STMS configuration (domain controller).
Costs and effort increase with the size of the system and the requirements for availability and data protection.