Food for thought for another productive system: until when must the system be identical, keyword: transaction log
Import of delta statuses after SAP system copy / restore
What is the purpose of copying a complete SAP system? - Well, there are several reasons. Test and development system: After a new productive system has been set up, at least one identical development system or even one test system is still needed. To avoid having to repeat the customizing (settings and configurations of the SAP modules and business processes) on these systems, it makes sense to make a copy. This is clearly the faster way to achieve the goal!
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.
Pre- and post-processing
"The creation of SAP system copies used to represent an enormous effort," says Martin Schulz from SAP Basis Administration. Almost 4,000 employees worldwide access our SAP systems directly. If the SAP systems are down, then nothing works in many departments - and that certainly happened in the past. Although the actual copying process is completed in just a few hours, the manual post-processing - which includes, for example, adjusting parameters, users and rights, profiles, system settings and interfaces - can take up to a week. This keeps the entire seven-person SAP Basis team busy.
Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.
In addition, an authorization concept for the system copy is required to protect the authentic data it contains.