Technical system copy for the upgrade
Scope of the SAP system copy
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.
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).
Test and training system: data anomyization, migration of master data, migration of user data / passwords
SAP upgrade: Before a very extensive SAP upgrade, you may want to test the run and analyze any errors that occur, especially if the development and test systems are not allowed to be down for too long. In that case, it's best to do this on a system copy.
Depends on the extent of splitting and the degree of parallelization. When importing, the limiting factor is often the index structure.
SAP system copy is made much easier by the "Shortcut for SAP Systems" application.
The important thing is to think about the target system before building it.
At the same time, their system landscapes are becoming increasingly complex due to mergers and acquisitions and the use of new technologies.