SAP system copy Job logic instead of customizing

Direkt zum Seiteninhalt
Job logic instead of customizing
SAP system clone and copy
One to two pre-tests are required, one of which should be performed on the production system. The additional load on the production system caused by the IMIG has been negligible. Split/mirror techniques allow many actions to be moved from the production machine to another machine.

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).
Key solution steps
Quasi tick boxes instead of time-consuming handling of programming lines, so that the use is also possible for less experienced experts who have never or only few SAP system copies created. And this after little system training.

Installation continues until the 'Load Data' phase. Here the program waits for successfully exported packages and starts the import as soon as a package has been exported.

"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.

Technically, it is quite possible to build up a degree of automation here as well, but officially certified consultants ("migration consultants") are required to perform the heterogeneous system copy.

One of these acts as a backup system.
SAP Corner
Zurück zum Seiteninhalt